CVE-2026-87029

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-102347 (ENISA EUVD) · GHSA-55wc-3pg8-jfw6 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici is an HTTP client library for Node.js. In versions 7.15.0 through 7.30.0 and 8.0.0 through 8.12.1, its decompress interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw, and while undici's engine converts a synchronous throw from a downstream handler into a per-request failure, that protection is absent when the throw happens asynchronously from a zlib callback. As a result, a downstream handler that throws by design, such as the built-in dump interceptor which throws when a response exceeds its configured maximum size, escapes as an uncaught exception that terminates the Node.js process. A malicious or compromised HTTP server can crash any client that composes the decompress interceptor with such a handler by returning a small compressed body that decompresses to more than the configured limit, so only the decompressed size matters and the bytes on the wire stay tiny. The issue is fixed in undici 7.30.1 and 8.12.2, and users should upgrade to one of those versions or later. As a workaround, avoid composing the decompress interceptor with a response handler that throws during response processing until upgrading.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.3%
EPSS %ILE
17th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

October 15, 2026

Last Modified

October 19, 2026

Advisory Details (2)

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

undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-55wc-3pg8-jfw6
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-87029(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs26-main-26.11.1-0.4.hum12026-10-19redhat
redhatnodejs24-main-24.21.0-1.5.hum12026-10-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • 7.15.0 up to 7.30.1: fixed in 7.30.1
  • 8.0.0 up to 8.12.2: fixed in 8.12.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-27 18:30 UTCEG score recompute
  7. 2026-10-27 18:30 UTCVendor advisory
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-25 13:54 UTCEG score recompute
  12. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-19 20:47 UTCEG score recompute▲ 1.60
  18. 2026-10-19 20:47 UTCVendor advisory
  19. 2026-10-19 20:45 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  22. 2026-10-18 03:04 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  24. 2026-10-16 20:33 UTCEG score recompute
  25. 2026-10-16 20:13 UTCEG score recompute
Show 4 more
  1. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-10-15 19:37 UTCEG score recompute
  3. 2026-10-15 19:01 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  4. 2026-10-15 18:57 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-87029?
CVE-2026-87029 is a high-severity vulnerability; its CVE record was published on October 15, 2026. undici is an HTTP client library for Node.js. In versions 7.15.0 through 7.30.0 and 8.0.0 through 8.12.1, its decompress interceptor forwards decompressed response data to the downstream handler from zlib stream event callbacks without catching exceptions those callbacks may throw, and while…
When was the CVE record for CVE-2026-87029 published?
The CVE record for CVE-2026-87029 was published on October 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-87029 actively exploited?
CVE-2026-87029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87029?
CVE-2026-87029 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-87029?
A fix for CVE-2026-87029 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87029 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-87029

Explore →

Is Your Infrastructure Affected by CVE-2026-87029?

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

Book a Demo →Browse All CVEs