PHP maintainers announced a critical security release for all supported PHP versions, scheduled to ship between 14:00 and 14:30 UTC on November 19. The release is expected to fix CVE-2026-115560, a remote code execution flaw in session upload progress handling, and arrives weeks after two other PHP flaws were added to CISA’s exploited-vulnerabilities list.
What the PHP Maintainers Announced for the Four-Week Release Cycle
The maintainers pre-announced the release on Wednesday as part of their regular four-week security cycle. The highest severity rating among the fixes is “critical,” but the announcement states that the critical issues depend on non-default configurations or uncommon setups. The exact list of CVEs and the fixed version numbers are to be published when the release lands.
Because the release covers every supported branch, organizations running multiple PHP versions will need to update each one separately.
How CVE-2026-115560 Is Triggered in Session Upload Progress
CVE-2026-115560 is a remote code execution flaw in session upload progress. It is triggered only when an application sets the session.serialize_handler directive to php_binary or php_serialize and then switches it to php at runtime with ini_set() before calling session_start(). Session upload progress must also still be enabled.
PHP described the flaw in an informational advisory on October 23. Elizabeth Barron of the PHP Foundation said in October that exploiting it requires “a very unlikely combination of configuration and specific PHP application code.” The emergency releases issued that month did not include a fix for it.
Disabling Session Upload Progress as the Interim Mitigation
Until the patch is applied, the recommended mitigation is to set session.upload_progress.enabled to 0 and restart PHP workers. That setting removes one of the preconditions the attack depends on.
Status of Exploit Claims Around CVE-2026-115560
No exploitation of CVE-2026-115560 has been confirmed. Some GitHub repositories claim to hold exploit code, but a researcher cited in coverage of the release says none of them are confirmed to work. The narrow configuration requirement limits the practical risk, although PHP powers a large share of the web, including WordPress.
The October PHP2Shell Flaws Set the Backdrop
The release lands against the background of the PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which each carry a 9.2 severity score. PHP shipped emergency fixes for them on October 21, and CISA added both to its Known Exploited Vulnerabilities catalog on October 26. Suspected Chinese actors used them against Palo Alto Networks and Check Point gateways, according to reporting on the campaign.
Censys data indicates that more than half of exposed servers remain unpatched against PHP2Shell. That backlog is likely to shape how security teams treat this release: the PHP2Shell episode showed that flaws in the language runtime can be exploited quickly and can reach network gateways.
Why Configuration-Dependent PHP Flaws Still Draw Attention
A flaw that requires an unusual combination of settings and application code is normally a low-probability target. The difference this time is context. Attackers have already shown interest in PHP vulnerabilities this season, and public repositories claiming exploits, even unverified ones, give opportunistic actors something to test against.
The PHP Foundation’s own description of the combination as “very unlikely” is a fair measure of the bar for exploitation. Applications that never touch session.serialize_handler at runtime fall outside the vulnerable pattern.
Update Guidance for PHP Administrators Ahead of the Release
The maintainers’ guidance is to update as soon as the release is published and restart PHP workers so the new code is loaded. Where an immediate update is not possible, disabling session upload progress closes the specific path used by CVE-2026-115560.
Once the final advisory lists the complete set of CVEs and version numbers, the picture of how many of the fixes are configuration-dependent will be clear. For now, the notable points are the breadth of the affected versions and the October history that makes a PHP security notice harder to dismiss.
