PHP-FPM request smuggling enables RCE
High risk · public exploit
Risk assessment
PHP-FPM HTTP request smuggling lets unauthenticated attackers forge backend requests and run PHP code. Update to 8.2.36, 8.3.37, 8.4.28 or 8.5.13.
What to do
Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.
- No fixed version listed yet. Restrict exposure and watch the vendor advisory. NVD references
- Remediation and Mitigation in this advisory
Exploitation confirmed - public proof-of-concept - CVE-2026-129289 is a critical request smuggling flaw in PHP-FPM (PHP before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28, and 8.5.* before 8.5.13) that lets an unauthenticated remote attacker forge backend FastCGI requests and execute attacker-controlled PHP code. Patches shipped in 8.2.36, 8.3.37, 8.4.28 and 8.5.13; update immediately.
Overview
CVE-2026-129289 is a request smuggling vulnerability in PHP-FPM. When a PHP application opens php://input but does not read the request body to the end, PHP fails to discard the unread bytes when the request shuts down. If the front-end server keeps backend connections alive, those leftover bytes remain on the wire.
The exploit requires connection reuse, which is off by default in nginx and Apache. It becomes reachable when nginx runs with fastcgi_keep_conn on or Apache mod_proxy_fcgi uses enablereuse=on. In that configuration, PHP-FPM treats the residual bytes as the start of a new FastCGI request.
An attacker sends a single crafted multipart/form-data request. The leftover body is parsed as a fresh backend request, letting the attacker set parameters such as SCRIPT_FILENAME, REMOTE_ADDR and PHP_ADMIN_VALUE. Chosen values can redirect execution to an uploaded or writable PHP file, spoof the client address so IP-based access controls are bypassed, and inject PHP configuration directives. The result is remote code execution without authentication. Deployments using LSAPI can also see follow-on requests on the connection disrupted.
The CVSS score is 9.2, reflecting network attack vector, low complexity, no privileges and no user interaction. EPSS estimates a 17.0 percent probability of exploitation in the next 30 days. CISA KEV does not currently list this CVE, so there is no confirmed active exploitation, but the low barrier to weaponizing the flaw makes prompt patching important.
Impact
Successful exploitation gives an unauthenticated attacker code execution in the PHP-FPM worker context, typically the web server user. From there an attacker can read application secrets, pivot to internal services, or persist. Sites that reuse backend connections are the primary exposure. Any application that reads php://input partially, such as upload handlers that inspect only headers, should assume risk until patched.
Remediation and Mitigation
- Upgrade PHP to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 as applicable.
- If you cannot patch immediately, disable backend connection reuse: remove
fastcgi_keep_conn onin nginx, or setenablereuse=offin Apachemod_proxy_fcgi. - Review application code for
php://inputreads that stop before end-of-body and drain or reject unread data. - Audit reverse proxies and load balancers for connection reuse settings that could expose the backend.
Recent supply chain incidents such as the SAP npm packages compromised in a credential-stealing attack and the Apache ActiveMQ CVE-2026-34197 KEV addition show how quickly internet-facing middleware becomes a target once a bypass exists.
Security Insight
Request smuggling keeps re-emerging because it lives in the seam between two components that each assume the other will enforce boundaries. PHP-FPM trusting residual bytes on a reused connection mirrors past HTTP desync bugs in reverse proxies, where parsers disagreed about message length. The fact that this is a default-off configuration issue rather than a default-on flaw may lull teams into delay, but any environment that tuned for performance with keepalive reuse is silently exposed.
Further Reading
Exploit references 2 PoC Show
Public PoC References
Unverified third-party code
These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).
Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.
| Repository | Stars |
|---|---|
| tc4dy/CVE-2026-129289-PoC-Exploit CVE-2026-129289 (CVSS 9.2) PHP-FPM FastCGI Record Smuggling Red/Blue team toolkit. Multipart HTTP exploit, DNS/HTTPS exfil, SOCKS/Tor proxy support, and header-based version checks, plus direct socket | ★ 5 |
| LLCForge/CVE-2026-129289 PHP-FPM FastCGI Record Smuggling RCE | ★ 0 |
Showing 2 of 2 known references. Source: nomi-sec/PoC-in-GitHub.
Get a Telegram alert when the next one lands: PHP advisories