Skip to content
All posts

PHP 8.5.13 Security Release: FPM Smuggling RCE, What to Do

November 21, 2026 · Team PlayCISO
TL;DR · the short version

PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (and 8.6.0) on 19 November 2026. Three of the fixes are rated CVSS v4.0 9.2 by PHP and each depends on a setup detail: CVE-2026-129289, PHP-FPM request smuggling when an application leaves part of the request body unread and the web server reuses FastCGI connections (for example nginx fastcgi_keep_conn on or Apache enablereuse=on, neither the default), which PHP says can lead to attacker-controlled PHP code running; CVE-2026-129474, a use-after-free in PHP 8.5 only that php.ini-production prevents by enabling zend.exception_ignore_args; and CVE-2026-115560, a session serializer mismatch reachable through session upload progress, which the release now turns off by default. CISA's enrichment says no exploitation for any of them, and none is in KEV. Upgrade, then check FastCGI connection reuse, which php.ini each server loads, and any explicit session.upload_progress.enabled=1.

Put it into practice
Set the patch deadline for your PHP estate
Score PHP-FPM hosts by exposure, exploit likelihood and business impact, next to the phpAfterShell and PHP2Shell work from the same weeks.
Open the Vulnerability Prioritizer

PHP's 19 November security releases fix three critical flaws that each hinge on a configuration detail: FastCGI connection reuse, a missing production php.ini, and session upload progress. On 19 November 2026 PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (and PHP 8.6.0). Among the fixes, PHP rates three at CVSS v4.0 9.2: CVE-2026-129289, PHP-FPM request smuggling; CVE-2026-129474, a use-after-free in PHP 8.5; and CVE-2026-115560, a session serializer mismatch. CISA's enrichment of the CVE records says no exploitation for any of them, and none is in its Known Exploited Vulnerabilities catalog.

Who this is for: CISOs, vulnerability-management and platform leads, and teams running PHP behind nginx or Apache, PHP container images or products that ship their own PHP.

Based on the CVE records PHP published, NVD, the CISA KEV catalog, php.net and the PHP ChangeLog, and the php-src source, all read on 21 November 2026. PlayCISO is not affiliated with the PHP project. We describe each flaw at the level PHP's own records do and publish no exploit details.

Confirmed vs not yet known

PHP confirms (CVE records, ChangeLog): all three CVEs, their CVSS v4.0 9.2 scores, the affected ranges below and the fixed releases of 19 November 2026. PHP says CVE-2026-129289 needs backend connection reuse, which is not the nginx or Apache default, and that php.ini-production prevents CVE-2026-129474.

CISA: its enrichment says "Exploitation: none" for all three, "Automatable: yes" for CVE-2026-129289 and "no" for the other two. None was in the KEV catalog dated 20 November.

NVD: all three "Awaiting Analysis"; the only score is PHP's.

Not established: any exploitation or public proof of concept; a workaround PHP itself labels as one for CVE-2026-129289; and whether PHP 8.1 or older builds carry the CVE-2026-129474 flaw (PHP's record lists 8.5 only). We could not open PHP's GitHub advisory pages from our session, so this post relies on the CVE records PHP published, which link to them.

The three CVEs at a glance

CVE (PHP advisory)What PHP saysAffectedCondition that matters
CVE-2026-129289 (GHSA-qc49-hpvq-g2w6)PHP-FPM request smuggling through an unread HTTP request body; can lead to execution of attacker-controlled PHP code. CVSS v4.0 9.2, AV:N/AC:L/AT:P/PR:N/UI:N.Before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13 (sapi-fpm)Front end reuses backend connections: e.g. nginx fastcgi_keep_conn on, Apache mod_proxy_fcgi enablereuse=on
CVE-2026-129474 (GHSA-8mjj-2r7p-4hg2)Use-after-free in magic method (__call(), __callStatic()) backtraces; can lead to remote code execution. CVSS v4.0 9.2, AC:H/AT:P.8.5 before 8.5.13 onlyzend.exception_ignore_args off (PHP's built-in default) with fatal_error_backtraces on (the default); php.ini-production prevents it
CVE-2026-115560 (GHSA-658j-r8rw-q6mx)Session serializer mismatch can lead to remote code execution, session corruption or denial of service. CVSS v4.0 9.2, AC:H/AT:P.Before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13 (ext-session)Session upload progress on, and a session written with php_binary or php_serialize but read with php

CVE-2026-129289: PHP-FPM request smuggling

PHP's record says that when an application opens php://input without reading it to the end, PHP does not discard the unread part of the body at request shutdown. If the web server keeps the FastCGI connection open for the next request, PHP-FPM can read those leftover bytes as a new request. PHP says an unauthenticated attacker can use a single crafted multipart request to forge a backend request with chosen parameters such as SCRIPT_FILENAME, REMOTE_ADDR and PHP_ADMIN_VALUE, "which can lead to execution of attacker-controlled PHP code". With LSAPI, later requests on the connection can be disrupted.

The exposure turns on connection reuse. PHP names nginx with fastcgi_keep_conn on and Apache mod_proxy_fcgi with enablereuse=on as examples, and says reuse is not the default in either. It is often turned on for performance, so check rather than assume. CISA's enrichment rates it "Automatable: yes", the only one of the three it marks that way. PHP credits Stephan Lipp and David Korczynski (Ada Logics / Anthropic) and Aviral Srivastava as reporters.

CVE-2026-129474: PHP 8.5 without the production php.ini

When PHP builds a backtrace for a method call handled by __call() or __callStatic(), it can read stale values that point to freed memory. PHP says that if a fatal error such as exceeding memory_limit happens as the application enters such a call, an attacker who controls enough request data to influence memory allocation may corrupt memory, crash the worker or, with knowledge of memory addresses, run code. It needs fatal_error_backtraces on (the default) and zend.exception_ignore_args off.

The setting is the dividing line. In the php-src source, zend.exception_ignore_args defaults to off; php.ini-production sets it On and php.ini-development sets it Off. So a PHP 8.5 server running with no php.ini, the development file, or a container image that never copied a production ini in is the case to look for. Only PHP 8.5 is listed as affected.

Useful next, if this was relevant to you

Showing 1 of 3: CISO Readiness Scorecard

CVE-2026-115560: session serializer mismatch

This is the issue behind PHP's 23 October advice to set session.upload_progress.enabled=0, which PHP then called "an unlikely RCE vector" needing "an unusual combination of configuration and application code". Its record says upload progress can store attacker-controlled data in a session key using the php_binary or php_serialize serializer; if the same session is later read with the php serializer (changed at runtime, or different between applications sharing a session store), bytes inside the key reach the unserializer and objects can be injected. In the php-src source, the built-in default for session.upload_progress.enabled is 1 in 8.5.12 and 0 in 8.5.13 and 8.2.36. An explicit =1 anywhere in your configuration overrides that.

The same session extension also got the phpAfterShell fix in these releases; see our phpAfterShell post for CVE-2026-126714 and CVE-2026-129481. If you are still finishing the October work, PHP2Shell is the one in KEV.

What else is in the release

By our count from the PHP 8 ChangeLog, 8.5.13 and 8.6.0 list 18 CVE IDs, 8.4.28 lists 14, 8.3.37 lists 13 and 8.2.36 lists 12. Besides the three above and the session fixes, they include an FPM use-after-free that can lead to local privilege escalation (CVE-2026-129291), an FPM status page XSS (CVE-2026-129292), a PHP-CGI out-of-bounds read and write (CVE-2026-129538) and a PHAR signature bypass (CVE-2026-128090). php.net's release posts say only "This is a security release"; on 18 November it said the critical issues "require either non-default configuration or uncommon setups". Take the whole release.

Timeline

DateEventSource
22 Oct 2026CVE-2026-115560 reserved by PHP as CNACVE record
23 Oct 2026PHP informational advisory: set session.upload_progress.enabled=0 until the next release (CVE-2026-115560)php.net
13 Nov 2026CVE-2026-129289 reservedCVE record
15 Nov 2026CVE-2026-129474 reservedCVE record
18 Nov 2026PHP announces security releases for 19 November, 14:00-14:30 UTC, highest severity CRITICALphp.net
19 Nov 2026PHP releases 8.5.13, 8.4.28, 8.3.37, 8.2.36 and 8.6.0; the three CVE records are published between 14:42 and 14:44 UTCphp.net, ChangeLog, CVE records
19-20 Nov 2026CISA enrichment: "Exploitation: none" for all three; "Automatable: yes" for CVE-2026-129289CVE record
21 Nov 2026Not in CISA KEV (catalog of 20 November); NVD status "Awaiting Analysis"CISA KEV, NVD

What security leaders should do this week

  • Upgrade every PHP that serves web traffic to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (or your distribution's fixed package), restart PHP-FPM and the web server, and check the version the web server actually runs. Rebuild and redeploy container images on PHP bases, and ask vendors whose products ship PHP for their fixed build.
  • Find FastCGI connection reuse. Search nginx configs for fastcgi_keep_conn on and Apache configs for enablereuse=on on PHP-FPM backends, and include load balancers and platform images you did not write. Those hosts go to the front of the queue for CVE-2026-129289.
  • Check which php.ini each PHP 8.5 server loads (php --ini, and phpinfo() on a non-public path for the FPM side). No ini or the development ini means zend.exception_ignore_args is off; set it On as php.ini-production does, then upgrade.
  • Look for an explicit session.upload_progress.enabled=1 in php.ini, FPM pools, vhosts and .user.ini files. If nothing uses upload progress bars, remove it so the new default (off) applies, and make sure no code switches session.serialize_handler at runtime.
  • Unsupported PHP (8.1 and older): PHP's record for CVE-2026-129289 covers every version before 8.2.36 and the project ships no fix for those branches. Get a vendor-supported build or record the exception with an owner and a date in your risk register.
  • Set the deadline with data. None is in KEV today, but CVE-2026-129289 is rated automatable. Use the SSVC calculator and track the fix dates in the remediation SLA tracker.

PHP has not published indicators for these three flaws, so we do not suggest a specific hunt. For all of PHP's 2026 flaws on one page, see PHP in the Breach Index. These are vulnerabilities in PHP, not a breach of the PHP project.

Frequently asked questions

Which PHP versions fix CVE-2026-129289, CVE-2026-129474 and CVE-2026-115560?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, released on 19 November 2026, plus PHP 8.6.0, released the same day. CVE-2026-129474 only affects PHP 8.5, so it is fixed in 8.5.13 and listed in the 8.6.0 ChangeLog. PHP 8.1 and older get no updates from the PHP project; ask your distribution or LTS vendor.

What is CVE-2026-129289?

A PHP-FPM request smuggling flaw rated CVSS v4.0 9.2 by PHP. When an application opens php://input but does not read the body to the end, PHP does not discard the rest at shutdown. If the web server reuses backend connections to PHP-FPM, the leftover bytes can be parsed as a new FastCGI request with parameters the attacker chose, which PHP says can lead to execution of attacker-controlled PHP code. It affects PHP before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13.

Is CVE-2026-129289 a problem with nginx fastcgi_keep_conn?

It needs connection reuse between the web server and PHP-FPM. PHP's CVE record names nginx with fastcgi_keep_conn on and Apache mod_proxy_fcgi with enablereuse=on as examples, and says reuse is not the default in nginx or Apache. The bug is in PHP, so upgrading PHP is the fix; the setting decides whether a server is reachable by this route. PHP says LSAPI setups can see later requests on the connection disrupted.

Does CVE-2026-129474 affect me if I use php.ini-production?

PHP says php.ini-production prevents it, because that file turns zend.exception_ignore_args on. It affects PHP 8.5 before 8.5.13 when fatal_error_backtraces is on (the default) and zend.exception_ignore_args is off, which is PHP's built-in default and the php.ini-development setting. Servers running with no php.ini, a development php.ini or container images without a production ini are the ones to check. Upgrade either way.

What is CVE-2026-115560?

A session serializer mismatch in PHP that PHP rates CVSS v4.0 9.2. With session upload progress enabled, a multipart upload can place attacker data in a session key written with the php_binary or php_serialize serializer; if the session is later read with the php serializer (changed at runtime, or different between applications sharing a session store), objects can be injected. PHP's 23 October notice called it an unlikely RCE vector needing an unusual configuration.

Did the November PHP release turn off session upload progress?

Yes, in the source we checked. The built-in default of session.upload_progress.enabled changed from 1 in PHP 8.5.12 to 0 in 8.5.13 (and is 0 in 8.2.36). An explicit session.upload_progress.enabled=1 in php.ini, an FPM pool or a vhost still turns it on, so look for one.

Are these PHP CVEs being exploited?

No exploitation has been reported. CISA's enrichment of all three CVE records says "Exploitation: none", none is in CISA's Known Exploited Vulnerabilities catalog (checked 21 November 2026), and NVD has not yet analysed them. CISA marks CVE-2026-129289 "Automatable: yes", so do not wait for KEV to patch it.

Was PHP hacked?

No. These are vulnerabilities in PHP, not a breach of php.net or the PHP project. The exposure is to organisations running unpatched PHP.

Sources

Set the patch deadline for your PHP estate
Score PHP-FPM hosts by exposure, exploit likelihood and business impact, next to the phpAfterShell and PHP2Shell work from the same weeks.
Open the Vulnerability Prioritizer
Take this with you
The three CVEs at a glance · CVE-2026-129289: PHP-FPM request smuggling · CVE-2026-129474: PHP 8.5 without the pro… · CVE-2026-115560: session serializer mism… · What else is in the release · Timeline

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro