CVE-2026-129289

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 16% (97th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-130243 (ENISA EUVD)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 16%CVSS: 9.2Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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 before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.

CVSS
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
16%
EPSS %ILE
97th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
16% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 22, 2026

Advisory Details (1)

Auto-updated Nov 19, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

PHP-FPM request smuggling through an unread HTTP request body · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatphp8.4-0:8.4.28-1.el10_22026-11-21redhat
redhatphp:7.4-8100020261119125714.f79986652026-11-21redhat
redhatphp:8.3-9080020261120133305.92026-11-21redhat
redhatphp:8.2-9080020261120141350.92026-11-21redhat
redhatphp8.4-0:8.4.28-1.el10_32026-11-20redhat

These rows come from Red Hat. Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 06:36 UTCVendor advisory
  2. 2026-11-22 00:29 UTCEchelonGraph re-scored
  3. 2026-11-22 00:29 UTCVendor advisory
  4. 2026-11-22 00:13 UTCVendor advisory
  5. 2026-11-21 23:46 UTCEchelonGraph re-scored
  6. 2026-11-21 23:46 UTCVendor advisory
  7. 2026-11-21 16:38 UTCEPSS rescoreEPSS 16% · 97th percentile
  8. 2026-11-21 16:28 UTCVendor advisory
  9. 2026-11-20 16:45 UTCEchelonGraph re-scored
  10. 2026-11-20 16:36 UTCEPSS rescoreEPSS 17% · 97th percentile
  11. 2026-11-20 05:28 UTCEchelonGraph re-scored
  12. 2026-11-20 04:57 UTCEchelonGraph re-scored
  13. 2026-11-19 20:28 UTCEchelonGraph re-scored
  14. 2026-11-19 19:43 UTCEchelonGraph re-scored
  15. 2026-11-19 18:28 UTCEchelonGraph re-scored
  16. 2026-11-19 17:33 UTCEchelonGraph re-scored
  17. 2026-11-19 16:03 UTCENISA EUVD ID recordedEUVD-2026-130243 · Source: ENISA EUVD
  18. 2026-11-19 15:28 UTCEchelonGraph re-scored
  19. 2026-11-19 14:48 UTCEchelonGraph re-scoredFirst assessed: 9.2 CRITICAL
  20. 2026-11-19 14:48 UTCMITRE cvelistV5first tracked

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCtc4dy/CVE-2026-129289-PoC-Exploit
    Published Nov 21, 2026

    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 RCE, webshell planting, reverse shells, safe FPM probes, and JSON reporting. Built for authorized security testing.

    Open source ↗
  • GitHub PoCLLCForge/CVE-2026-129289
    Published Nov 20, 2026

    PHP-FPM FastCGI Record Smuggling RCE

    Open source ↗

Frequently asked(5)

What is CVE-2026-129289?
CVE-2026-129289 is a critical-severity vulnerability; its CVE record was published on November 19, 2026. 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…
When was CVE-2026-129289 made public?
CVE-2026-129289 was made public on November 19, 2026: that is the date its CVE record's CNA, PHP Group, gives for when the vulnerability was made public. The CVE record itself was published on November 19, 2026. EchelonGraph's copy of the record carries a last-modified date of November 22, 2026; the record at its source may have been updated since.
Is CVE-2026-129289 actively exploited?
CVE-2026-129289 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129289?
CVE-2026-129289 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129289?
A fix for CVE-2026-129289 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129289 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-129289 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-129289

Explore →

Is Your Infrastructure Affected by CVE-2026-129289?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.