According to the PHP advisory, a remote unauthenticated attacker may turn leftover body data into a new backend request when the front end reuses a persistent connection. The forged request can bypass front-end routing and lead to PHP code execution with the worker's privileges.The PHP CVE record rates the flaw 9.2 Critical under CVSS 4.0. The documented attack requires backend connection reuse and an application path that opens the request-body stream without consuming it fully. The PHP advisory says standard nginx and Apache configurations that close each backend connection are outside the demonstrated PHP-FPM attack.
What it allows
How Does CVE-2026-129289 Cross the PHP-FPM Boundary?
PHP opens the request-body stream lazily. The advisory says request shutdown wrongly treated an opened stream as a consumed body, leaving unread data on a persistent backend connection. PHP-FPM could then interpret that leftover data as another FastCGI request. The front end had neither created nor authorized that second request.
An attacker must reach a route that opens the body stream without fully reading it. The advisory says a malformed multipart request can cause the parser to stop early, leaving attacker-controlled bytes for the reused connection. The forged backend request may bypass route checks and run attacker-controlled PHP as the worker. This is the PHP-FPM impact; the advisory establishes only request-stream disruption for LSAPI.
What Does the Risk Evidence Establish?
The PHP CVE record assigns CVSS 4.0 9.2 Critical, with network reach, no required privileges, and no user interaction. It also marks attack requirements as present, reflecting the required deployment and application conditions. CISA's catalog version 2026.11.18 did not list this CVE when checked on 19 November 2026. Catalog status does not establish whether exploitation has occurred.
We recommend prioritizing Internet-facing PHP-FPM deployments with backend connection reuse. Teams can place the affected runtime and connection setting in their vulnerability intelligence workflow to separate exposed instances from PHP installations without the documented conditions.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 8.2.x | 8.2.0 to before 8.2.36 | 8.2.36 |
| 8.3.x | 8.3.0 to before 8.3.37 | 8.3.37 |
| 8.4.x | 8.4.0 to before 8.4.28 | 8.4.28 |
| 8.5.x | 8.5.0 to before 8.5.13 | 8.5.13 |
For distribution packages and custom builds, check the supplier’s advisory.
Compare the running PHP-FPM or LSAPI runtime, then verify backend connection reuse. Distribution backports require package-advisory verification.
Which PHP Versions and Configurations Are Affected?
The PHP advisory lists 8.2.0 through 8.2.35, 8.3.0 through 8.3.36, 8.4.0 through 8.4.27, and 8.5.0 through 8.5.12. PHP lists fixed releases 8.2.36, 8.3.37, 8.4.28, and 8.5.13. The PHP changelog confirms the CVE fix in each of those four releases.
For the demonstrated PHP-FPM code-execution path, the front end must reuse its backend connection. The advisory names nginx with persistent FastCGI connections enabled and Apache mod_proxy_fcgi with connection reuse enabled as examples. A route must also open the input stream without reading it fully. The same cleanup flaw can disrupt later LSAPI requests on persistent connections, but the advisory does not establish LSAPI code execution.
Use the patch management process to confirm the running PHP-FPM binary after the change. The vulnerability management guide explains how to record the affected service and retest its exposure.
Timeline
- 2026-11-19
PHP published GHSA-qc49-hpvq-g2w6 and its CVE record for the unread-body request smuggling flaw.
- 2026-11-19
PHP changelog listed the fix in 8.2.36, 8.3.37, 8.4.28, and 8.5.13.
What to do
-
Inventory affected runtimes
Record the running PHP-FPM and LSAPI versions for each application. Check the backend connection reuse setting and whether application paths open input without consuming it fully.
-
Install the fixed PHP release
Upgrade PHP 8.2 to 8.2.36, 8.3 to 8.3.37, 8.4 to 8.4.28, or 8.5 to 8.5.13. For distribution packages, confirm the vendor has backported this CVE fix.
-
Verify the running fix
After deployment, check the PHP-FPM or LSAPI process version, restart the relevant service, and confirm the live runtime matches the patched build or a documented backport.
-
Reduce exposure while patching
Disable persistent backend connection reuse at the front end until the fixed PHP runtime is active. Keep PHP-FPM and LSAPI listeners away from untrusted networks.
-
Review suspicious request handling
Examine web and PHP-FPM logs for unexpected backend script execution or routing mismatches. Treat this as an investigative check, not proof of exploitation by itself.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-129289 in Brandefense Atlas
The Atlas record of CVE-2026-129289: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can CVE-2026-129289 execute PHP code without authentication?
The PHP advisory says a remote unauthenticated attacker can execute PHP code as the worker when backend reuse and an unread-body application path are present.
Which PHP releases fix CVE-2026-129289?
PHP lists 8.2.36, 8.3.37, 8.4.28, and 8.5.13 as the fixed releases for their respective branches.
Do default nginx and Apache FastCGI settings expose the demonstrated attack?
The PHP advisory says standard configurations that close the backend connection after each request are outside the demonstrated PHP-FPM attack.
Does the advisory establish LSAPI remote code execution?
No. It describes LSAPI request-stream disruption on persistent connections but does not establish the PHP-FPM code-execution chain for LSAPI.
Sources
- PHP-FPM request smuggling through an unread HTTP request bodyPHP Group
- CVE-2026-129289 RecordPHP CVE Numbering Authority
- PHP 8 ChangeLogPHP Group
- Known Exploited Vulnerabilities CatalogCISA