CVE
PHP remote code execution via unread request bodies
- Exploited
- No known exploitation
- Fix
- Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Summary
PHP (PHP-FPM) can mishandle an unread HTTP request body when an application opens php://input without reading it fully. In setups where the web server reuses backend connections, which is not the default in nginx or Apache, a remote attacker with no login can send one crafted multipart request to forge a backend request and potentially run attacker-controlled PHP code.
Original description
PHP-FPM request smuggling through an unread HTTP request body.
PHP does not discard the unread part of an HTTP request body at request shutdown when the application has opened php://input without reading it to the end. When the front end reuses backend connections, which is not the default in nginx or Apache (for example nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on), PHP-FPM can parse the leftover bytes as a new FastCGI request. An unauthenticated remote attacker can use a single crafted multipart/form-data 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, subsequent requests on the connection can be disrupted.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 48 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129289 (PHP-FPM request smuggling through an unread HTTP request body), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129289 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.2.0, fixed in 8.2.36; from 8.3.0, fixed in 8.3.37; from 8.4.0, fixed in 8.4.28; from 8.5.0, fixed in 8.5.13
Fixed versions: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129289 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129289 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129289
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129289"}.Timeline
- cve.now early warning
PHP readies critical updates to patch RCE flaw CVE-2026-115560
1 day - CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- PHP Group PHP
From 8.2.0 · fixed in 8.2.36; From 8.3.0 · fixed in 8.3.37; From 8.4.0 · fixed in 8.4.28; From 8.5.0 · fixed in 8.5.13
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-qc49-hpvq-g2w6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129289 |
| Record | NVD · CVE-2026-129289 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129289
Is CVE-2026-129289 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-129289?
PHP: from 8.2.0 before 8.2.36; from 8.3.0 before 8.3.37; from 8.4.0 before 8.4.28; from 8.5.0 before 8.5.13.Source: cve.now feed data
How do I fix CVE-2026-129289?
Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.Source: cve.now feed data