Threat advisory 8 min read

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36: seven critical bugs fixed, three of them left over from PHP2Shell

The PHP release of 19 November 2026 fixes seven critical bugs, among them PHP-FPM request smuggling. What each one needs, the fixed versions, and what to set until you update.

A cracked purple PHP logo held together with steel staples and riveted plates while a welding torch seals one crack, next to the words PHP and 7 critical fixes, in a dark workshop

On 19 November 2026 the PHP project released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, on the same day as the first PHP 8.6.0 release. The patch releases fix seven bugs that PHP rates critical, each with a CVSS 4.0 score of 9.2. Five advisories describe a path to code execution with the privileges of the PHP worker; for the other two, PHP has shown memory corruption but not code execution. SecurityWeek counts ten more fixes rated high or medium in the same releases.

The release comes four weeks after PHP2Shell, the two bugs fixed on 21 October (our note on those). Three of the new advisories continue that story. One is an incomplete fix of CVE-2026-109619, one covers more ways to reach the same stale backtrace, and one is the session upload progress issue PHP announced on 23 October and held for this release.

There is one difference that matters. PHP2Shell hit default installs. For this release, PHP's advance notice says the critical issues "require either non-default configuration or uncommon setups". That does not make them safe to skip: whether a setup is uncommon depends on the front end, the configuration of each PHP-FPM pool and the application code, and few teams know all three by heart.

The seven advisories

BugBranchesWhat the attack needs
CVE-2026-129289, PHP-FPM request smuggling8.2 to 8.5A front end that reuses FastCGI connections, and an endpoint that opens php://input without reading it to the end
CVE-2026-126714, partly overwritten session files8.2 to 8.5The default files session handler, influence over session contents, an interrupted write, and an object gadget chain in the application
CVE-2026-115560, session serializer mismatch8.2 to 8.5Session upload progress on, and one session store written and read with different session.serialize_handler values
CVE-2026-129481, use-after-free after an interrupted session shutdown8.3 to 8.5A fatal error in a callback during session shutdown, such as the stream_close() of a stream wrapper
CVE-2026-129182, stale fatal error backtrace8.5Path-specific INI settings that fail when PHP restores them at shutdown
CVE-2026-129474, use-after-free in __call() backtraces8.5fatal_error_backtraces=1 (the 8.5 default) and zend.exception_ignore_args=0
CVE-2026-129496, timezone cache use-after-free8.2 to 8.5A startup warning written to a file-based error_log, for example from an invalid date.timezone

Fixed in 8.2.36, 8.3.37, 8.4.28 and 8.5.13. PHP 8.1 and older get no release from the PHP project, and the upload progress advisory notes that releases older than 8.2 may also be affected. If you run one of those, ask your distribution or LTS vendor.

CVE-2026-129289: look at this one first

The other six are memory or deserialization bugs that need a particular heap layout, a gadget chain or an unusual setting. This one needs none of that. It works with a stock PHP configuration, and one request is enough to run PHP code chosen by the attacker. What decides exposure is the front end in front of PHP-FPM:

How an unread request body becomes a second FastCGI request1A front end keeps one FastCGIconnection to PHP-FPM openacross requests2The attacker sends a malformedmultipart body that makes the PHPparser stop at a known offset3The application opens php://inputand does not read it to the end4PHP finishes the request withoutdiscarding the unread body bytes5PHP-FPM reads those bytes as a newFastCGI request on that connectionand runs it
The attack needs a front end that keeps FastCGI connections open between requests.

The application side is common: PHP's advisory points at frameworks that create an input stream before routing or authentication, even on endpoints that never use the body. The front end side is the setting to check. The advisory lists nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy setups that keep backend connections, and LSAPI. Standard nginx and Apache configurations close the FastCGI connection after each request and are not affected by the demonstrated attack.

Besides running code, the smuggled request can call PHP scripts that the front end never routes to, hand the application a forged client address, and change administrator-level PHP settings for later requests.

Sessions: two new bugs and one leftover

CVE-2026-126714 sits in the files session handler, the default. When PHP updates a session it writes the new data into the existing file without clearing it first. If the write stops partway, the file holds the start of the new session and the end of the old one, and carefully arranged data can turn ordinary string bytes into serialized objects on the next session_start(). Code execution then needs a gadget chain in the application. Session backends that replace records atomically avoid this particular defect.

CVE-2026-115560 is the upload progress issue from October. Upload progress writes data with one serializer, and a context that reads the same session with the php serializer can take part of a session key for object data. The fix turns session upload progress off by default and refuses runtime changes to session settings while it is on. An explicit session.upload_progress.enabled=1 in your configuration overrides the new default, so check for one.

CVE-2026-129481 is an incomplete fix of PHP2Shell's CVE-2026-109619. A fatal error in a callback during session shutdown leaves the worker holding a pointer to the script filename after the request memory is freed, and the next request on that worker can free it again. PHP 8.2 does not have the affected field. No setting closes this one.

PHP 8.5 backtraces and the timezone cache

CVE-2026-129474 is a use-after-free when PHP collects the arguments of a method handled by __call() or __callStatic() for a backtrace. Frameworks use those magic methods for logging facades, database layers and service proxies. The demonstrated remote attack sends a crafted JSON body that causes a fatal error while the application enters such a method. It needs fatal error backtraces, which PHP 8.5 turns on by default, and arguments in backtraces. php.ini-production sets zend.exception_ignore_args=1, which blocks this path; the built-in default does not.

CVE-2026-129182 extends the October fix for the fatal error backtrace. Two shutdown cases can fill the backtrace again after it was cleared: a max_memory_limit set both globally and per path, and a zlib.output_compression setting that conflicts with a per-path output_handler. .user.ini can supply the zlib settings.

CVE-2026-129496, on all four branches, is the odd one out: a warning written to a file-based error_log while PHP starts up leaves a reference to freed memory that the first request of each worker can reach.

What to do

  1. Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or to a distribution package that carries these fixes. Then restart the PHP-FPM master and every pool, or Apache when you run mod_php. Several of these bugs live in state a worker keeps between requests, and a worker started before the update keeps running the old code.
  2. Check the version of the binary that serves web requests, not only php -v. The command line and PHP-FPM are separate binaries with separate configuration.
  3. PHP 8.2 reaches end of life on 31 December 2026. If you are on it, plan the move to 8.3 or newer now.

If you cannot update today

PHP's advisories list these measures. Each one narrows a specific attack path; none of them is a fix.

  • Request smuggling (CVE-2026-129289): turn off FastCGI connection reuse in the front end. In nginx, leave fastcgi_keep_conn off, which is its default. In Apache, do not set enablereuse=on. Other front ends should close the backend connection after each request. Never expose a PHP-FPM or LSAPI listener to an untrusted network.
  • Session files and upload progress (CVE-2026-126714, CVE-2026-115560): set session.upload_progress.enabled=0 in php.ini or the FPM pool, not with ini_set() or .user.ini, and restart the workers. Keep untrusted data out of sessions where you can.
  • PHP 8.5 backtraces (CVE-2026-129474, CVE-2026-129182): set fatal_error_backtraces=0 and zend.exception_ignore_args=1 in the configuration the workers read, pool settings included, and restart them. Changing only the command line php.ini does nothing for PHP-FPM, and display_errors=0 does not stop PHP from building the backtrace.
  • Timezone cache (CVE-2026-129496): fix the configuration errors and deprecated settings that make PHP warn at startup, then restart the master and all workers. Sending PHP errors to syslog instead of a file also avoids the demonstrated trigger.
  • Interrupted session shutdown (CVE-2026-129481): no setting helps. Turning off upload progress does not touch this path, and OPcache alone is not reliable. Update.

Two searches show where to start. File locations differ between distributions.

# FastCGI connection reuse in the web server
grep -Rn "fastcgi_keep_conn\|enablereuse" /etc/nginx /etc/apache2 /etc/httpd 2>/dev/null

# The settings above in the PHP and PHP-FPM configuration
grep -Rn "upload_progress\|fatal_error_backtraces\|exception_ignore_args\|serialize_handler" /etc/php* /etc/php-fpm* 2>/dev/null

Sources