PHP Fixes Seven Critical Bugs Today. Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Turning Off Upload Progress Covers Only Part of It.

PHP shipped security releases today, November 19, at about 14:05 UTC. Upgrade to the fixed version for your branch: PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36. PHP rates seven of the fixed bugs CRITICAL. If you cannot upgrade today, set "session.upload_progress.enabled = 0" in php.ini and in every PHP-FPM pool, then restart every worker. That one setting closes the attack path for CVE-2026-115560 and part of CVE-2026-126714. It does not cover the other five critical bugs. Their workarounds are listed below.
What is confirmed
PHP announced the release on November 18 and said the critical issues "require either non-default configuration or uncommon setups." The release landed today on php.net, with 17 advisories published on PHP's GitHub repository between 14:05 and 14:08 UTC.
Fixed versions, per the php.net ChangeLog:
- PHP 8.5: 8.5.13 (18 CVEs)
- PHP 8.4: 8.4.28 (14 CVEs)
- PHP 8.3: 8.3.37 (13 CVEs)
- PHP 8.2: 8.2.36 (12 CVEs)
No other branches got a release today. PHP's advisory for CVE-2026-115560 says the feature dates to PHP 5.4.0, so "older unsupported releases may also be affected."
PHP's severity counts across the 17 advisories: 7 critical, 4 high, 6 medium. One more CVE, CVE-2026-48841, is a bundled uriparser library update in 8.5.13 only.
The seven critical bugs, each rated 9.2 by PHP:
- CVE-2026-115560, session serializer mismatch, all four branches. This is the bug PHP pre-disclosed on October 23. Session upload progress writes attacker-supplied data in one session format. If something later reads the same session in the "php" format, part of the key is passed to unserialize. With a suitable gadget class in the application, that is code execution. PHP's advisory says the reporter showed command execution with a Guzzle gadget on 8.2.35, 8.3.36, 8.4.27 and 8.5.12, and with a Monolog 2.11.1 gadget. The mismatch can come from an app switching session.serialize_handler at runtime. It can also come from two apps, pools, virtual hosts or command-line jobs that share one session directory with different settings. Separate FPM pools do not get separate session storage by default.
- CVE-2026-126714, partially overwritten session files, all four branches. It affects the default "files" session handler. An interrupted write can leave a file holding parts of two sessions, which can lead to deserializing attacker data. Turning off upload progress removes one input path. It does not fix apps that store attacker-controlled data in the session themselves.
- CVE-2026-129289, PHP-FPM request smuggling, all four branches. Unread request-body bytes on a reused FastCGI connection can become a second request. PHP says an unauthenticated attacker can execute attacker-controlled PHP code. Workaround: turn off backend connection reuse. Leave nginx "fastcgi_keep_conn" off and Apache "enablereuse" off. Never expose an FPM listener to untrusted networks.
- CVE-2026-129481, use-after-free after interrupted session shutdown, 8.3 and later. PHP calls this an incomplete fix for CVE-2026-109619, one of the PHP2Shell bugs. Upload progress settings do not help here. Workaround for FPM: "pm.max_requests = 1", at a performance cost.
- CVE-2026-129496, timezone cache use-after-free, all four branches. It is triggered by diagnostics written to a PHP error log file during startup. Workaround: fix the configuration errors and deprecated settings that produce startup warnings, or log to syslog, then restart the master and all workers.
- CVE-2026-129474, use-after-free in magic method backtraces, 8.5 only. It needs "fatal_error_backtraces = 1" (the 8.5 default) and "zend.exception_ignore_args = 0". The php.ini-production file sets exception_ignore_args to 1. Workaround: set "zend.exception_ignore_args = 1" or "fatal_error_backtraces = 0".
- CVE-2026-129182, stale fatal-error backtrace after shutdown, 8.5 only. Another follow-on to CVE-2026-109619. Workaround: "fatal_error_backtraces = 0".
The rest, as PHP rates them. High: CVE-2026-129291 (PHP-FPM epoll use-after-free, local privilege escalation), CVE-2026-128064 (mixed-case HTTPS and FTPS URLs can send data in plaintext), CVE-2026-128090 (Phar OpenSSL signature bypass), CVE-2026-127960 (denial of service through folded HTTP response headers). Medium: CVE-2026-129292 (FPM status page XSS), CVE-2026-129538 (PHP-CGI out-of-bounds read and write during PATH_INFO correction), CVE-2026-129506 and CVE-2026-15353 (SOAP), CVE-2026-129438 (URI serialization, 8.5 only), CVE-2026-129501 (DOM double free, 8.4 and 8.5).
The fix changes a default. PHP says the update disables session upload progress by default and blocks runtime changes to session settings while upload progress is on. An explicit "session.upload_progress.enabled = On" in your configuration still wins. If you need the feature, every app and process that can read or write the same session store must use the same session.serialize_handler, even after the update. PHP does not enforce that for you.
What is not known
Whether any of these bugs is being exploited. None of the 17 advisories we read says so, and none links to a public exploit. The CVE-2026-115560 advisory describes the reporter's own demonstrations, which is not the same as attacks in the wild. We have not seen press or vendor reports of exploitation as of this writing. PHP2Shell went from fix to mass exploitation within hours in October, so do not wait for that answer.
Whether distributions have shipped backports yet. Check your vendor's tracker.
What to do
- Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, then restart PHP-FPM, Apache or whatever runs PHP. A running worker keeps the old code until it restarts.
- If you run a distribution package (Debian, Ubuntu, RHEL, Alma, Rocky, SUSE), the version number may not change. Vendors backport fixes into their own versions. Check the package changelog for the CVE IDs, for example "apt changelog php8.3-fpm | grep CVE-2026-115560" or "rpm -q --changelog php-fpm | grep CVE-2026-115560". "php -v" alone does not tell you.
- Rebuild container images. Pulling a new base image does nothing for containers already running. Rebuild from the updated "php:" tag or your patched base, redeploy, and confirm the version inside the running container.
- Until you can upgrade, set "session.upload_progress.enabled = 0" in php.ini and every FPM pool file, not with ini_set() in code. PHP says ini_set() is too late. Then apply the workarounds above that match your setup: turn off FastCGI connection reuse, quiet startup warnings or log to syslog, and on 8.5 set "fatal_error_backtraces = 0".
- After upgrading, search your configuration for an explicit "session.upload_progress.enabled = On". If you do not use upload progress bars, remove it.
Am I affected?
Run "php -v" on each host and inside each container. Anything below 8.5.13, 8.4.28, 8.3.37 or 8.2.36 on an upstream build is affected, unless your distribution's changelog lists the CVEs. Run "php --ini" to see which php.ini the command line loads. The web server may load a different one. For PHP-FPM, run "php-fpm -i | grep session.upload_progress.enabled" (the binary may be named php-fpm8.3 or similar) and grep your pool files for "session.upload_progress" and "serialize_handler". The command-line "php -i" reports the CLI settings, which can differ from what your web workers use. If more than one app or pool shares a session.save_path, compare their session.serialize_handler values. A mismatch there, with upload progress on, is the CVE-2026-115560 setup. For CVE-2026-129289, check your nginx config for "fastcgi_keep_conn on" and Apache for "enablereuse=on" in front of PHP-FPM.
How we know
We read php.net's news page, the PHP 8 ChangeLog and the 17 advisories on PHP's GitHub repository (php/php-src) after they went up between 14:05 and 14:08 UTC. Every version number, CVE, severity and workaround above comes from those pages. A press report announced the release ahead of time. We could not load it (HTTP 403) and did not rely on it.
Our edge cannot see these bugs. CVE-2026-115560 rides inside a multipart upload body, and the FPM smuggling bug happens between your web server and PHP-FPM. Neither leaves a path or user agent our instruments record. We have no indicators to add to our feed. PHP published none, and none appeared in the sources we read.
Sources
- php.net news, November 18 pre-announcement and November 19 releases: https://www.php.net/
- PHP 8 ChangeLog: https://www.php.net/ChangeLog-8.php
- PHP security advisories on GitHub: https://github.com/php/php-src/security/advisories
- CVE-2026-115560 advisory, GHSA-658j-r8rw-q6mx: https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx
- CVE-2026-129289 advisory, GHSA-qc49-hpvq-g2w6: https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
Read next
The October bugs these follow on from: PHP2Shell: the fix is out. Patch PHP today.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.