PHP is pushing critical security updates today — November 19, between 14:00 and 14:30 UTC — including a fix for CVE-2026-115560, a remote code execution bug tied to the session upload progress feature. If you can’t patch in that window, you can close this door with one INI line right now.
The One-Line Fix
Before anything else: add this to your php.ini or PHP-FPM pool configuration and restart your PHP worker.
session.upload_progress.enabled = 0
That’s the mitigation. session.upload_progress.enabled is a PHP_INI_PERDIR directive, so it must be set in php.ini, a PHP-FPM pool config, or .htaccess under mod_php — not via ini_set() at runtime, because it needs to apply before request parsing begins. Apply, restart, then patch when the release lands.
What the Vulnerability Actually Is
Session upload progress has been enabled by default since PHP 5.4. The feature tracks file upload progress by writing client-supplied filenames and form field names into the session store while the upload is happening — before any of your PHP code runs. That last part is what matters here.
CVE-2026-115560 exploits an edge case: if your app sets session.serialize_handler to php_binary or php_serialize in its configuration, then switches the handler to php using ini_set() before calling session_start(), the session data already written by upload progress can be deserialized with the new handler — opening a path to code execution.
Elizabeth Barron, executive director of the PHP Foundation, was direct about the scope: “CVE-2026-115560 requires a very unlikely combination of configuration and specific PHP application code, which we do not expect to occur in practical use of PHP.”
So this is not Log4Shell. It is not a broad-blast RCE that hits everyone. It requires non-default session configuration plus a runtime handler switch — a setup you’d have to deliberately build. No active exploitation has been reported as of late October. That said: the mitigation costs you nothing, the feature is rarely needed, and PHP’s own documentation has recommended disabling it for years when you’re not building upload progress bars. There is no good reason to leave it on.
Versions Receiving the Patch
Today’s release covers all currently supported PHP branches:
- PHP 8.2.x
- PHP 8.3.x
- PHP 8.4.x
- PHP 8.5.x
If you’re on PHP 8.1, you’re out of luck — it reached end-of-life and will not receive this fix. The mitigation INI setting still works, but that’s as much coverage as you’re getting. This is a reasonable forcing function to finally upgrade.
The PHP2Shell Context
CVE-2026-115560 is the third bug in the PHP2Shell cluster. The first two — CVE-2026-109618 and CVE-2026-109619 — were significantly more serious: pre-disclosure exploitation was recorded starting October 17, emergency patches shipped October 21, and both landed on CISA’s Known Exploited Vulnerabilities list within days. Cloudflare deployed WAF rules. NCSC Netherlands published a full operational response guide.
This third one was disclosed on October 23 without an emergency fix — the PHP Foundation described it as lower risk and said a standard bugfix release would handle it. That bugfix release is today. The Register covered the advance notice yesterday.
The pattern is worth noting: two critical exploited vulnerabilities followed within days by a third that required its own security advisory. PHP’s security posture has been under a microscope since October. Whether that changes the calculus for your infrastructure is a conversation worth having with your team.
What to Do
- Set
session.upload_progress.enabled = 0in your PHP config now - Restart your PHP worker
- Apply the patch when it drops between 14:00 and 14:30 UTC today
- If you’re on PHP 8.1, upgrade — this won’t be the last CVE you miss
The patch is coming in hours. The mitigation takes thirty seconds. Apply both.

