The release at a glance
Security firm Aikido says that PHP released security updates for all supported versions on 19 November 2026 and that the release fixes 18 CVEs, including CVE-2026-129289, a critical PHP-FPM request smuggling flaw (CVSS 9.2). BleepingComputer also reports the figure of 18, crediting Aikido. According to that report, the fixes cover PHP's core engine, session handling, PHP-FPM, CGI and other components.
PHP's own 8.5.13 announcement calls it a security release and asks all PHP 8.5 users to upgrade. It also says Windows source and binaries are available on the official downloads page, so Windows-hosted PHP is covered too.
The patched version for each branch:
| Branch | Patched version |
|---|---|
| PHP 8.5 | 8.5.13 |
| PHP 8.4 | 8.4.28 |
| PHP 8.3 | 8.3.37 |
| PHP 8.2 | 8.2.36 |
Why the count depends on your branch
The headline number is 18, but your branch may receive fewer fixes. A breakdown published by HOL says PHP 8.5.13 lists 17 advisories in total, 8.4.28 lists 14, 8.3.37 lists 13 and 8.2.36 lists 12. A separate DEV Community summary says the release notes list 12 CVEs fixed on every supported branch, plus more on the newer ones. Newer branches contain newer code, and some of the bugs live only in that code. Aikido's 18 and the per-branch advisory counts don't match, likely because they were counted differently. Either way, the action is the same: install the patched release for your branch.
Section summary: All four supported branches have patched releases out now, including Windows builds. How many fixes you get depends on your branch, and 8.5 gets the most.
The critical bug: CVE-2026-129289, PHP-FPM request smuggling
PHP's own GitHub advisory, titled "PHP-FPM request smuggling through an unread HTTP request body," rates this bug Critical with a CVSS 4.0 base score of 9.2. The affected range is 8.2.0 up to 8.2.36, 8.3.0 up to 8.3.37, 8.4.0 up to 8.4.28, and 8.5.0 up to 8.5.13.
How it works
FastCGI and LSAPI can carry several requests over a single connection. Before PHP takes the next request on that connection, it has to read the rest of the previous request's body or close the connection. Here is how the attack works, according to the advisory:
- When an application opens
php://input, PHP creates a stream for the request body but reads it lazily. - During request shutdown, PHP took the existence of that stream as proof that the body had been handled. It then skipped the usual cleanup that discards unread input.
- The attacker sends a malformed
multipart/form-databody that makes PHP's multipart parser stop at a predictable point. If the application opensphp://inputwithout reading it all, attacker-controlled bytes stay on the connection. The advisory notes that frameworks which create an input stream before routing or authentication can trigger this even when the endpoint never uses the body. - With
FCGI_KEEP_CONNenabled, PHP-FPM keeps the connection open and reads the leftover bytes as a new FastCGI request. The web server never created or authorized that request. - The forged request controls FastCGI parameters, including
SCRIPT_FILENAME,REMOTE_ADDRandPHP_ADMIN_VALUE. An attacker who knows the path of any existing PHP script can turn onallow_url_includeand pointauto_prepend_fileatphp://input. The forged request's own body then runs as PHP.
The advisory says the attack needs one request, with no memory corruption, no knowledge of memory addresses and no race condition. It also warns that the changed admin-level settings can stay active for later requests handled by the same worker.
Who is exposed
This is where the scary number needs context. Exploitation requires two things: a front end that keeps backend connections open, and an application path that opens php://input without reading all of it. The advisory names these risky setups:
- nginx with
fastcgi_keep_conn on - Apache
mod_proxy_fcgiwithenablereuse=on - HAProxy FastCGI applications that keep backend connections open
- LSAPI
Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated attack. For LSAPI, the advisory describes desynchronization and disruption of later requests, but it does not establish arbitrary code execution, because LSAPI doesn't use the PHP_ADMIN_VALUE mechanism.
The bug also goes back further than the supported branches. The PHP advisory traces it to the lazy php://input handling introduced in PHP 5.6.0. HeroDevs' vulnerability listing agrees, saying the affected range includes the End-of-Life release lines starting from 5.6. If you're still running 7.4 in a corner of your infrastructure, you're in scope and won't get an official fix.
Hosting panel vendor ApisCP gives a useful example of practical triage. In its own release assessment, it marked this CVE as not applicable to its stack because it requires enablereuse=on in mod_proxy_fcgi. That's the kind of check every admin should run against their own configuration.
Section summary: CVE-2026-129289 is serious but depends on your configuration. Persistent backend connections are the key condition. If you've turned on connection reuse, treat this as urgent.
The rest of the fixes
BleepingComputer's report lists these other notable vulnerabilities:
- CVE-2026-129474: use-after-free involving magic-method backtraces, potentially leading to RCE
- CVE-2026-129496: timezone-cache use-after-free, potentially leading to RCE
- CVE-2026-126714: partially overwritten session files, potentially leading to RCE
- CVE-2026-115560: session serializer mismatch, potentially leading to RCE
- CVE-2026-129291: PHP-FPM epoll use-after-free, potentially leading to local privilege escalation
- CVE-2026-128090: PHAR OpenSSL signature bypass via algorithm downgrade
The DEV Community summary of the release notes adds several fixes that matter for Windows and web deployments. They include CVE-2026-129538 | CGI | PHP-CGI out-of-bounds read and write during PATH_INFO correction, a PHP-FPM status endpoint XSS (CVE-2026-129292), and two SOAP flaws: a use-after-free when processing DTD entity references and information disclosure through malformed array dimensions. It also lists two Streams bugs: mixed-case HTTPS and FTPS URLs can expose data in plaintext, and a denial of service through folded HTTP response headers. Aikido's table lists a few more, including CVE-2026-129501 | DOM | Double free during DOM XML serialization and a URI-layer upgrade to uriparser 1.0.3.
Some fixes apply only to certain branches. Lilting.ch's breakdown marks CVE-2026-129474 as 8.5 only, triggered by a fatal error when entering a magic method such as __call(). The same analysis notes a session-shutdown use-after-free, CVE-2026-129481, which it describes as missed in php2shell. That suggests this release partly cleans up after the earlier PHP2Shell emergency patches.
The note for Windows shops
PHP-FPM is largely a Unix-world tool. In our experience, PHP on Windows under IIS usually runs php-cgi.exe through the FastCGI module, so the headline FPM bug probably isn't your biggest risk. That doesn't let you off the hook. The PHP-CGI out-of-bounds bug in PATH_INFO handling, the SOAP and DOM memory-safety flaws, the PHAR signature bypass and the Streams plaintext issue are all in the CGI layer or core extensions, which Windows builds also include. PHP has published Windows builds for the patched versions, so updating is straightforward.
Section summary: This release isn't only about the FPM bug. The engine, session, CGI, SOAP and Streams fixes reach most deployments, including Windows ones.
What to do now
Step 1: Upgrade
Install 8.5.13, 8.4.28, 8.3.37 or 8.2.36, depending on your branch. Every mitigation below is a temporary measure until you do.
Step 2: If you can't patch today, close the smuggling path
PHP's advisory recommends turning off backend connection reuse:
- nginx: leave
fastcgi_keep_conndisabled - Apache: leave
enablereusedisabled inmod_proxy_fcgi - Other FastCGI front ends (HAProxy included): configure them to close the backend connection after every request
The advisory says that reading php://input to the end before every request finishes would block the demonstrated condition. It warns, however, that error paths, resource exhaustion and application shutdown make this unreliable as your only defense.
Step 3: Address the session bugs
According to BleepingComputer, PHP first disclosed CVE-2026-115560 in an informational advisory on October 23. Its temporary mitigation was to set session.upload_progress.enabled=0 in php.ini and restart PHP workers. Lilting.ch also lists other temporary workarounds for engine bugs, such as zend.exception_ignore_args=1 for the 8.5-only backtrace issue. Treat these as stopgaps, not fixes.
Step 4: Check your network exposure
Aikido and the PHP advisory agree on this one: PHP-FPM and LSAPI listeners should never be directly reachable from untrusted networks. If port 9000 is open to the internet, close it today.
Step 5: Find out what's in your containers
Aikido says it has published hardened container images with backported fixes. Its table shows tags such as php:8.4.27-fpm | PHP 8.4.28 (backported). BleepingComputer reports that Aikido's images also cover unsupported versions back to 5.6, and that third-party maintainer Ondřej Surý has released patched packages for unsupported branches. These are third-party builds, not official PHP releases. They can buy time on legacy systems, but they're no substitute for moving to a supported branch.
How to confirm success: after upgrading and restarting PHP-FPM or your web server's FastCGI pool, php -v should show the patched version. A phpinfo() page served through your actual web front end should show it too. Check both: a CLI binary that's up to date doesn't prove the FPM pool is.
The bigger picture
The PHP security team's advance warning said that updates for all supported versions were coming, and BleepingComputer quotes the team as saying the critical issues "require either non-default configuration or uncommon setups." That's accurate, but it understates things. Connection reuse to FastCGI backends is a common performance tweak, and tuning guides often recommend it. A setting that's "non-default" can still be widespread.
The smuggling bug also follows a familiar pattern: two components that each work fine on their own disagree about where one request ends and the next begins. HTTP desync attacks have been a staple of web security research for years. This one moves the problem behind the reverse proxy into the FastCGI connection. Your WAF in front won't see the forged request, because the front end never sends it.
Is anyone exploiting this yet? None of the sources reviewed here report attacks in the wild. Still, the PHP advisory describes the exploitation chain in detail, and the October advisory had already pointed attackers at the session code. Don't wait to find out. Patch, turn off connection reuse if you can't patch yet, and close any FPM port exposed to the internet. Windows admins should also patch: the FPM bug probably doesn't apply to them, but the CGI and core-extension fixes do.
References
- PHP security updates fix 18 flaws, including critical RCE bugs BleepingComputer · 2026-11-19T11:28:23-05:00
- PHP-FPM request smuggling through an unread HTTP request body · Advisory · php/php-src · GitHub github.com
- PHP schedules a critical security release for 19 November, including CVE-2026-115560 aikido.dev