Go straight to an AI summary of this blog post instead

  • Summarize this post with Perplexity
  • Summarize this post with Gemini

ELS for PHP Status for the November 19 PHP Security Release

TuxCare began shipping backported fixes for the November 19 PHP CVEs on release day. That includes the PHP-FPM smuggling bug, CVE-2026-129289. The CVEs fixed vary by PHP version, so check the erratum for your exact package.

The status for each CVE and PHP version appears in the TuxCare CVE Tracker as packages ship.

Get Endless Lifecycle Support for PHP →

Key Takeaways

  • PHP’s November 19 security release fixes 18 CVEs, and seven of them carry a critical 9.2 score.
  • CVE-2026-129289 lets one crafted request run PHP code where FastCGI connection reuse meets half-read request bodies.
  • Fixed versions are 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and PHP 8.1 and older get nothing upstream.
  • Several critical bugs date back to PHP 4 and 5, putting end-of-life PHP inside the affected range.

The Short Version

Jump to the Long Version ↓

What happened. On November 19, 2026, PHP shipped 8.5.13, 8.4.28, 8.3.37 and 8.2.36, plus the new 8.6.0, which already carries the fixes. Together they fix 18 CVEs, seven rated critical, a month after October’s PHP2Shell emergency patches. One of the new bugs comes from an incomplete PHP2Shell fix. Jump to this section →

Who’s affected. Each critical bug needs a particular setup. CVE-2026-129289 needs a web server that keeps FastCGI connections to PHP-FPM open, such as nginx with fastcgi_keep_conn on or Apache with enablereuse=on, plus an app that opens php://input without reading it all. Jump to this section →

How bad it is. PHP says its critical issues need uncommon setups, but the smuggling bug needs just one crafted request. Public proof-of-concept exploits exist for some of these bugs, but no confirmed attacks had been reported as of November 19. Jump to this section →

Where things stand. Upstream fixes cover 8.2 through 8.6, and Debian 12 and 13 have packages. PHP 8.1 and older get nothing upstream, and TuxCare’s backported PHP patches started landing for end-of-life versions on release day. Jump to this section →

What to do today. Upgrade the PHP workers serving traffic and restart them. Where that can’t happen today, turn off FastCGI connection reuse and set session.upload_progress.enabled=0. On PHP 8.5, also set zend.exception_ignore_args=1 and fatal_error_backtraces=0. Jump to this section → 

The Long Version

The release is a grab bag of bugs, most with very particular entry points. Some reports count 17 CVEs, others 18. Seventeen have php-src advisories, and the eighteenth comes from a bundled uriparser upgrade. Supported branches just need a version bump. The harder part is that several of these bugs reach back to PHP 4.1, 5.3, 5.4 and 5.6.

Seven Critical Bugs at a Glance

All seven score 9.2 under CVSS 4.0, but they’re not seven equal ways into a server.

CVE What it is What it needs
CVE-2026-129289 PHP-FPM request smuggling, unauthenticated code execution FastCGI connection reuse plus an app that leaves php://input partly unread
CVE-2026-115560 Session serializer mismatch, possible code execution Upload progress, mismatched serializers sharing the same session ID and storage, and a gadget chain
CVE-2026-126714 Partially overwritten session files, possible code execution Influence over session data, an interrupted write and a gadget chain
CVE-2026-129496 Use-after-free in the timezone cache A startup warning written to a PHP error log file, then an early diagnostic in a fresh worker
CVE-2026-129481 Use-after-free after an interrupted session shutdown A fatal error during session cleanup, then worker reuse (8.3 and later)
CVE-2026-129474 Use-after-free in magic method backtraces PHP 8.5 with fatal error backtraces and argument capture on
CVE-2026-129182 Use-after-free via a repopulated fatal error backtrace PHP 8.5 shutdown conditions plus an early diagnostic

The first four are fixed on all four maintenance branches and in 8.6.0. CVE-2026-129481 can’t exist on 8.2 because the field it abuses arrived in 8.3, and the last two come from fatal error backtraces, which are new in 8.5 and on by default.

How the FastCGI Smuggling Bug Works

CVE-2026-129289 is a plain logic bug, with no memory corruption involved. FastCGI lets one connection between the web server and PHP-FPM carry many requests. Before accepting the next one, PHP has to finish reading the previous request body or close the connection. When an app opens php://input, PHP creates a stream but reads it lazily. At shutdown, PHP treated the mere existence of that stream as evidence that the body had been handled and skipped the cleanup that throws unread bytes away.

An attacker sends a malformed multipart/form-data body that stops PHP’s multipart parser at a predictable spot. If the app opens php://input without reading to the end, which some frameworks do before routing or authentication, the leftover bytes stay on the connection. PHP-FPM then parses them as a new FastCGI request the web server never sent.

That’s a trust-boundary failure, because the forged request gets to set parameters like SCRIPT_FILENAME, REMOTE_ADDR and PHP_ADMIN_VALUE. With the path to any existing PHP script, an attacker can switch on allow_url_include and point auto_prepend_file at the request’s own body, so PHP runs whatever the body contains. The flaw dates to PHP 5.6.0.

The Session and Memory Bugs

CVE-2026-115560 is the bug PHP warned about on October 23, before it had a fix. Session upload progress writes attacker-controlled data with one serializer, php_binary or php_serialize. If an app reading the same session ID and storage uses the php serializer, part of a session key ends up in unserialize(), and researchers turned that into command execution with Guzzle and Monolog gadget chains. Upload progress arrived in PHP 5.4.0, and the fix turns it off by default.

CVE-2026-126714 hits the default files session handler. PHP overwrote session files without truncating them, so an interrupted write could glue one session’s start to another’s end, and carefully arranged data becomes objects on the next session_start(). The code dates to PHP 4.1.0.

CVE-2026-129481 comes from an incomplete fix for PHP2Shell’s CVE-2026-109619, and code execution through it hasn’t been shown. CVE-2026-129496 leaves a pointer to freed timezone-cache memory when a startup warning, such as an invalid date.timezone, lands in a PHP error log file. It has crashed FPM workers remotely, though code execution was only shown locally. The code goes back to PHP 5.3.18. The two 8.5-only bugs come from fatal error backtraces grabbing freed memory, with __call() and __callStatic() as the demonstrated route.

The Other Eleven Fixes

CVE-2026-129291 is a post-exploitation bug, so it needs code already running in a PHP-FPM worker. With catch_workers_output enabled, as it is in the official PHP-FPM Docker images, that code can corrupt the FPM master’s memory and run commands with the master’s privileges, which are often root on the host or inside the container. Chained with a remotely exploitable bug, it could carry an attacker from worker-level execution up to those privileges.

The others are narrower. CVE-2026-128090 stops a signed PHAR from being rewritten with a keyless hash signature, CVE-2026-128064 stops https:// and ftps:// URLs with uppercase letters in the scheme from going out in plaintext, and CVE-2026-127960 fixes quadratic-time parsing of folded HTTP headers. The rest cover PHP-CGI, the FPM status page, SOAP, DOM and the 8.5-only URI extension.

Who Is Actually Exposed

Start with the version. One host often runs several PHP builds (the CLI, an FPM pool, an Apache module, a container image), and php -v only describes the one in your shell.

PHP branch Security release on November 19
PHP 8.5, 8.4, 8.3, 8.2 8.5.13, 8.4.28, 8.3.37, 8.2.36
PHP 8.6 8.6.0 ships with the fixes
PHP 8.1 and older No upstream release, so verify a vendor backport

For CVE-2026-129289, does the front end reuse FastCGI connections, through fastcgi_keep_conn on in nginx, enablereuse=on on an Apache mod_proxy_fcgi backend or HAProxy holding FastCGI connections open? And can any route open php://input and leave data unread? LiteSpeed’s LSAPI shares the cleanup bug, though only request desync has been shown there. Stock nginx and Apache close the connection after each request, but tuned setups often turn reuse on.

For CVE-2026-115560, check session.upload_progress.enabled, which was on by default before this release. CVE-2026-126714 is different, since it affects the default files handler regardless of upload progress. On PHP 8.5, zend.exception_ignore_args=0 is PHP’s built-in default, but php.ini-production sets it to 1, so containers without a production php.ini are the ones to worry about.

How Hard This Is to Pull Off

Most of the criticals need a lot to line up, whether that’s a gadget chain in the app or heap grooming with known addresses. CVE-2026-129289 is the exception. Once the setup matches, it’s one request with no memory corruption and no race.

The 9.2 scores carry conditions too, flagged in the CVSS 4.0 vectors as attack requirements or high attack complexity. A PHP-FPM pool behind nginx with fastcgi_keep_conn on goes to the top of the list.

NHS England’s alert says multiple public proof-of-concept exploits exist for bugs in this release, without saying which bugs they target. No confirmed attacks had been reported as of November 19, but PHP2Shell drew exploitation attempts around its own disclosure, and detailed advisories give attackers a head start.

Which Distributions Have a Fix

Platform Status for CVE-2026-129289 on November 19, 2026
Debian 13 (php8.4) Fixed in 8.4.28-1~deb13u1 (DSA-6641-1)
Debian 12 (php8.2) Fixed in 8.2.36-1~deb12u1 in bookworm-security (DLA-4916-1)
Ubuntu Status varies by package and release, so check Ubuntu’s CVE page
PHP 8.1 and older from php.net No upstream fix

Check the Debian security tracker and the Ubuntu CVE page before acting, since packages land fast.

What This Means for Older PHP Versions

PHP 8.1 reached end of life at the end of 2025, and PHP 8.2 follows on December 31, 2026. PHP published source backports of the PHP2Shell fixes for 7.4, 8.0 and 8.1 in October, but not this time.

Old doesn’t mean out of range. The smuggling and session bugs sit in code going back to PHP 5.6, 5.4 and even 4.1, so most end-of-life PHP still carries them, and nothing upstream will patch it.

Stopgaps Until You Can Patch

If your web server reuses FastCGI connections to PHP-FPM, turn reuse off. In nginx, set fastcgi_keep_conn off; or remove the directive, since off is the default. In Apache, drop enablereuse=on from the FastCGI ProxyPass or BalancerMember line. Validate with sudo nginx -t or sudo apachectl configtest before reloading, and keep FPM and LSAPI listeners off untrusted networks. Don’t rely on the app reading php://input to the end instead, since PHP warns that error paths and shutdown can make that unreliable.

If you don’t need upload progress bars, set session.upload_progress.enabled=0. Set it centrally in php.ini or the FPM pool config and restart every worker. If you keep the feature, every app touching the same session store needs the same session.serialize_handler.

On PHP 8.5, set zend.exception_ignore_args=1 and fatal_error_backtraces=0. Together they cover both 8.5-only bugs.

Turn off catch_workers_output if you don’t need worker output in the logs. That removes CVE-2026-129291’s escalation path. Fixing startup warnings that land in a PHP error log file, such as a bad date.timezone, takes away the first step of CVE-2026-129496.

Each of these targets specific bugs. Until a fixed build is in, CVE-2026-129481 can be blocked in PHP-FPM with pm.max_requests=1 and a worker restart, at a real performance cost.

After upgrading, restart PHP-FPM or Apache, or redeploy the container. A new package on disk doesn’t replace an interpreter already in memory.

Checking a Server in a Few Minutes

php -v; php --ini; php-fpm -v 2>/dev/null || ls /usr/sbin/php-fpm* 2>/dev/null
php-fpm -i 2>/dev/null | grep -E 'session.upload_progress.enabled|session.serialize_handler|fatal_error_backtraces|zend.exception_ignore_args'
sudo nginx -T 2>/dev/null | grep -nE 'fastcgi_keep_conn|keepalive'
grep -rniE 'enablereuse' /etc/httpd /etc/apache2 2>/dev/null
grep -rnE '^[[:space:]]*(listen|catch_workers_output)[[:space:]]*=' /etc/php* /etc/opt 2>/dev/null
rpm -qa 'php*' 'alt-php*' 2>/dev/null; dpkg -l 'php*' 'alt-php*' 2>/dev/null | grep '^ii'

These give you a first inventory. php --ini describes the CLI’s configuration and php-fpm -i won’t show per-pool overrides, so check each active pool too (on Debian and Ubuntu, use a versioned name like php-fpm8.2). The rest cover connection reuse, pool listeners, worker output and package versions.

Where ELS Stands

Errata such as the ones for PHP 7.4 on Alpine Linux 3.24 and PHP 7.1 on Ubuntu 26.04 landed within hours of PHP’s release, each listing CVE-2026-129289 and CVE-2026-126714. Coverage runs from PHP 5.2 through 8.5, with the exact platform matrix in the ELS for PHP documentation.

Updates arrive through the TuxCare repositories with the package manager you already use, whether that’s yum, dnf, apt or apk. Restart PHP-FPM, Apache or the container afterward. Backported builds keep the familiar upstream version number, so check the erratum or the TuxCare CVE Tracker for your exact build instead of trusting php -v.

Get Endless Lifecycle Support for PHP →

A Patch Window Is Not an Upgrade Plan

Two critical PHP security releases in four weeks, and one of the new bugs exists because the last fix missed a path.

It’s tempting to read this as 18 flaws, four version numbers, done. The real work is finding the PHP behind each app, checking the risky settings and making sure every worker has restarted on a fixed build. Much of the vulnerable code has been sitting there for years.

Once a PHP branch hits end of life, upstream security releases stop, and staying patched means a specialist support provider or a migration. An unpatched PHP 7.4 app that reuses FastCGI connections and leaves request data unread faces the same smuggling risk as an unpatched 8.4 install, and the same gap shows up one layer up in Composer dependencies, which is the problem SecureChain for PHP addresses.

Close the connection reuse gap on exposed PHP-FPM pools today, restart rather than reload, and make sure your end-of-life PHP has a source of backported fixes before the next batch arrives.

Get Endless Lifecycle Support for PHP →

Timeline

Date Event
October 21, 2026 PHP fixes the PHP2Shell bugs, CVE-2026-109618 and CVE-2026-109619
October 23, 2026 PHP publishes a mitigation for CVE-2026-115560 ahead of a fix
November 19, 2026 PHP releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36, fixing 18 CVEs, alongside PHP 8.6.0
November 19, 2026 TuxCare publishes the first ELS for PHP errata with backported fixes
December 31, 2026 PHP 8.2 reaches end of life

Sources

PHP News Archive 2026

PHP 8 ChangeLog

GHSA-qc49-hpvq-g2w6, PHP-FPM request smuggling (CVE-2026-129289)

GHSA-658j-r8rw-q6mx, session serializer mismatch (CVE-2026-115560)

BleepingComputer, PHP security updates fix 18 flaws

The Hacker News, PHP fixes 7 critical flaws

Infosecurity Magazine, PHP releases patches to fix 18 vulnerabilities

Aikido, PHP critical security release analysis

NHS England Digital, PHP releases updates for multiple vulnerabilities

Debian security tracker, CVE-2026-129289

Ubuntu CVE-2026-129289

Join 4,500+ Linux & Open Source Professionals!

2x a month. No spam.

Table of Contents
Get the open-source security answers you need

Join 4,500+ Linux & Open Source Professionals!

2x a month. No spam.