Security Digest · Nov 19, 2026 · Vulnerability · Language runtime
PHP-FPM CVE-2026-129289: Request Smuggling to RCE
One request runs code in PHP-FPM when nginx, Apache or HAProxy reuse FastCGI connections. Fixed in 8.5.13/8.4.28/8.3.37/8.2.36. Check your front end.
Our verdict
Check exposure
Default nginx and Apache setups close the FastCGI connection after each request and are not exposed; if your front end reuses connections, patch or turn reuse off now, because one unauthenticated request runs code and a public exploit toolkit exists.
Who must act: Sites running PHP-FPM before 8.2.36, 8.3.37, 8.4.28 or 8.5.13 behind a front end that keeps FastCGI connections open: nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, or HAProxy fcgi-app with keep-conn (its default).
Who can relax: Stock nginx and Apache configurations that close the FastCGI connection after every request, plus mod_php and command-line-only PHP; LSAPI users should still patch, but PHP has not established code execution there.
- Affected
- PHP-FPM before 8.2.36
PHP-FPM 8.3.x before 8.3.37
PHP-FPM 8.4.x before 8.4.28
PHP-FPM 8.5.x before 8.5.13
End-of-life branches back to PHP 5.6.0 (per the advisory's code inspection) - Fixed in
- PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13 (Nov 19, 2026)
Ubuntu 26.04 php8.5 8.5.4-0ubuntu1.6
Ubuntu 24.04 php8.3 8.3.6-0ubuntu0.24.04.14
Ubuntu 22.04 php8.1 8.1.2-1ubuntu2.29 - CVSS
- 9.2 (v4.0, vendor)
- EPSS
- 16.1% (percentile 97)
- CISA KEV
- Not listed
- Exploitation
- Public proof-of-concept
- Severity
- Critical
What to do
- Check every front end for FastCGI connection reuse: nginx -T | grep fastcgi_keep_conn, grep -rni enablereuse /etc/apache2 /etc/httpd, and the fcgi-app sections of haproxy.cfg.
- Upgrade PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or your distribution's fixed package, and restart php-fpm.
- Until you can patch, turn reuse off: fastcgi_keep_conn off in nginx, drop enablereuse=on in Apache, add no option keep-conn to HAProxy fcgi-app sections, then reload.
- Rebuild container images from patched PHP bases and check bundled web server configs; Upwind says wodby/nginx images hard-code fastcgi_keep_conn on.
- Confirm the version that actually serves requests with php-fpm -v (or php-fpm8.3 -v) on each host and container.
How to check if you are affected or compromised
- If the FPM pool access log is enabled, look for requests PHP-FPM served that have no matching front-end access-log entry.
- Search PHP, PHP-FPM and web server error logs for the warning "File Upload Mime headers garbled", which Upwind saw on each smuggling attempt.
- Look for shells or downloaders started by php-fpm worker processes and for new PHP files in web roots.
What happened#
On November 19, 2026, PHP shipped security releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The most severe flaw they fix is CVE-2026-129289, which PHP's advisory describes as request smuggling in PHP-FPM, rated critical at CVSS 4.0 9.2. The day before, PHP's pre-announcement warned that the critical issues "require either non-default configuration or uncommon setups." This one fits that description, and whether you are exposed depends on the web server in front of PHP-FPM, not on PHP itself.
According to the advisory, PHP fails to discard an unread request body at the end of a request. When an application opens php://input without reading all of it, "PHP incorrectly treated the existence of this stream as evidence that the body had already been handled." An attacker can send a malformed multipart body that stops the parser at a predictable offset. The bytes after that point stay on the FastCGI connection. If the front end keeps that connection open for the next request, PHP-FPM reads the leftover bytes as a new, attacker-written FastCGI request.
The forged request "controls FastCGI parameters including SCRIPT_FILENAME, REMOTE_ADDR and PHP_ADMIN_VALUE." The advisory shows how that becomes code execution. Set allow_url_include=1 and auto_prepend_file=php://input, and the request body runs as PHP under the worker's account. The advisory says this needs no memory corruption, no address knowledge and no race condition. It adds that injected admin settings can persist for later requests handled by the same worker.
Who is affected#
PHP-FPM is affected before 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The advisory says the vulnerable code has been present since PHP 5.6.0, based on code inspection. End-of-life branches are therefore affected too and need a distribution or vendor backport. The CVE record does not list PHP 8.6.0, also released on November 19, as affected. Ubuntu has fixed packages for 26.04, 24.04 and 22.04 and for older releases under ESM. Red Hat scores the flaw 8.1 under CVSS 3.1 and points to its bulletin RHSB-2026-020.
Two more conditions must both hold. The first is an application code path that opens php://input without reading it to the end. Upwind says frameworks can do this "before routing or authentication." The second is a front end that reuses backend connections. The advisory names these:
- nginx with
fastcgi_keep_conn on. This is off by default. The maintainer of the anonaddy Docker image closed a report on that basis. - Apache
mod_proxy_fcgiwithenablereuse=on. - HAProxy FastCGI applications that keep backend connections. The HAProxy manual says of
option keep-conninfcgi-appsections: "By default, this option is enabled." HAProxy-to-FPM setups are therefore exposed unless someone turned the option off. - LiteSpeed LSAPI, where the advisory says the request stream can be desynchronized but "does not establish arbitrary code execution."
Upwind also reports that the wodby/nginx images hard-code fastcgi_keep_conn on.
Do you really need to act?#
Check first. If you find connection reuse, act today. The advisory says "standard nginx and Apache configurations that close the FastCGI connection after each request are not affected." For most PHP hosts, this release is a routine upgrade. Do not skip it, because BleepingComputer counts 18 CVEs in the batch, several of them RCE-class.
Connection reuse is a performance setting, so it tends to show up in tuned configs and container images rather than in distribution defaults. Where it is on, the bug is about as easy to exploit as web flaws get: one unauthenticated request leads to code execution. The CVE record now references a public exploit toolkit, whose README targets nginx, Apache, HAProxy and LSAPI. As of November 19, Upwind said none of the release's critical CVEs had been reported as exploited in the wild, and CISA's assessment in the CVE record lists exploitation as "none." The flaw is not in the KEV catalog. With a public tool available, expect scanning to start soon.
What to do now#
- Check each front end, including those inside containers:
- nginx:
nginx -T 2>/dev/null | grep -n fastcgi_keep_conn - Apache:
grep -rni enablereuse /etc/apache2 /etc/httpd - HAProxy: check
fcgi-appsections inhaproxy.cfgforno option keep-conn. Without that line, reuse is on.
- nginx:
- Upgrade to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or to your distribution's fixed package. Restart php-fpm and confirm the result with
php-fpm -v; the binary may be namedphp-fpm8.3or similar. - If you cannot patch yet, turn reuse off and reload. In nginx, set
fastcgi_keep_conn off;or remove the directive. In Apache, removeenablereuse=on. In HAProxy, addno option keep-conn. The advisory says that fully readingphp://inputin application code is not a reliable fix on its own. - Rebuild container images from patched PHP base images. Do not just restart old containers.
How to tell if you were hit#
In its lab, Upwind found that "each smuggling attempt left two traces." The first is a PHP-FPM access-log entry with no matching front-end request. You will only see this if the pool's access.log setting is enabled. The second is the PHP warning File Upload Mime headers garbled. Search PHP, PHP-FPM and web server error logs for that string. Also look for shells or downloaders started by php-fpm workers, and for new PHP files in web roots or upload directories. Smuggled admin settings can persist in a worker, so restart php-fpm after you patch or change the configuration.
Timeline#
- — CVE-2026-129289 is reserved.
- — PHP pre-announces a critical security release for the next day.
- — PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 ship. The GHSA and CVE record are published, and Ubuntu's CVE page lists fixed packages.
- — CISA's assessment in the CVE record lists exploitation as "none."
- — The CVE record, last updated today, references a public proof-of-concept toolkit.
Vulnerability records
- CVE-2026-129289 · PHP-FPM request smuggling through an unread HTTP request body.
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- PHP — GHSA-qc49-hpvq-g2w6: PHP-FPM request smuggling through an unread HTTP request body github.com
- CVE record — CVE-2026-129289 (PHP Group) cve.org
- PHP — Upcoming Critical PHP Security Release (Nov 18, 2026) php.net
- PHP — PHP 8 ChangeLog php.net
- Ubuntu — CVE-2026-129289 ubuntu.com
- Red Hat — CVE-2026-129289 access.redhat.com
- HAProxy — Configuration Manual (fcgi-app option keep-conn) docs.haproxy.org
- Aikido — PHP critical security release, 19 November (CVE-2026-129289, CVE-2026-115560) aikido.dev
- Upwind — PHP critical vulnerabilities: affected versions and mitigations upwind.io
- anonaddy/docker — Issue #465: FPM request-smuggling attack (CVE-2026-129289) github.com
Coverage and analysis
- BleepingComputer — PHP security updates fix 18 flaws, including critical RCE bugs bleepingcomputer.com