PHP disclosed a new vulnerability, CVE-2026-115560, on Oct. 24. The project described it as an "unlikely remote code execution path," saying three conditions must all be present for the issue to occur. The default configuration does not meet those conditions, and PHP has not assigned a severity score so far.
A patch is not available yet. PHP said the issue will go through the normal release process because the required combination is uncommon in practice, with the fix and a full advisory set to arrive in the next routine patch release. No date has been given.
Three conditions must all be met
According to the official notice, the problem only appears under a specific mix of configuration and application behavior. All three of the following conditions are required:
- The site sets
session.serialize_handlertophp_binaryorphp_serialize. - The application switches that value back to
phpwithini_set()before callingsession_start(). session upload progressremains enabled, which is the PHP feature used to track file uploads so a web page can display a progress bar.
The PHP manual states that the default value of session.serialize_handler is php, so the default setup does not satisfy the first condition. PHP also said sites that never change this setting during execution can keep upload progress enabled.
That means sites that do not switch the session serialization format in code are not affected by this issue.
Affected versions have not been listed
The notice does not list affected versions. It also does not say whether versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35, released on Oct. 21, include a fix for this issue. As a result, updating to those releases alone should not be treated as confirmation that the risk is gone.
Current guidance is to disable session upload progress
For sites that already disabled upload progress in response to the Oct. 21 GitHub security advisory GHSA-6wmf-4rv5-p3rp, which corresponds to CVE-2026-109619, PHP said no further action is needed.
For sites that have not done so, the recommendation is to set session.upload_progress.enabled=0 in php.ini, a PHP-FPM pool configuration, or another server-side setting that takes effect before request handling begins, and then restart all PHP workers.
PHP also pointed to an easy mistake: using ini_set() inside application code, or placing the setting in .user.ini, will not disable the feature.
Once disabled, upload pages that rely on session-based progress tracking will stop working. Sites that show upload progress bars should test their upload forms after making the change.
Patch timing is still unknown
The next step is to wait for the next routine patch release. PHP did not provide a release date. The report noted that PHP 8.5 routine releases have been arriving roughly every four weeks this year, but that is not an official commitment.
Until a patched release arrives, disabling upload progress remains the project’s recommended mitigation. The same advice applies even if a system is already running the Oct. 21 releases.
No exploitation mentioned as of Oct. 24
The Oct. 21 notice had already warned that upload progress is a feature that few people use and few people test, and said it should be turned off if it is not needed, even after updating. The PHP manual also advises applications that do not use upload progress bars to consider disabling the feature.
As for active attacks, PHP had not reported exploitation of the vulnerability as of Oct. 24. The U.S. Cybersecurity and Infrastructure Security Agency, or CISA, also did not include CVE-2026-115560 in its known exploited vulnerabilities catalog updated on Oct. 24.
A new CVE identifier does not automatically mean another large-scale security event. PHP’s own framing remains that the path is low probability. Until the project publishes a severity score, affected-version details, and a patch, disabling an unused feature is the main step it is recommending.


