CVE-2026-85024

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th 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 — 3 sources updated this week

Also known asEUVD-2026-71603 (ENISA EUVD) · GHSA-3wwx-pv8p-q78v (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici bundles a WebSocket client whose permessage-deflate size-limit cleanup removes all listeners from the internal zlib inflate stream, including its error listener, while that stream can still emit. When a remote peer sends a compressed payload that crosses the built-in 128 MiB decompressed-payload limit and then contains a malformed DEFLATE byte, the inflate stream emits a data error with no listener attached, which Node.js treats as a fatal unhandled error and terminates the entire process. Exploitation is remote and unauthenticated, requires no application mistake, and is asymmetric, since roughly 130 KB on the wire expands past the limit and crashes the process, and reconnecting can repeat the crash. This affects undici versions from 6.25.0 up to 6.28.1, from 7.28.0 up to 7.29.1, and from 8.1.0 up to 8.10.2. Users should upgrade to undici 6.28.1, 7.29.1, or 8.10.2.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
35th
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 (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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.

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

September 4, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 4, 2026
Patch available. Sources: github.
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
GitHub advisoryMentions a patch (unverified)

undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-3wwx-pv8p-q78v

Vendor Advisories for CVE-2026-85024(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs24-main-24.21.0-1.hum12026-09-23redhat
redhatnodejs26-main-26.8.2-0.1.hum12026-09-11redhat
redhatgrafana12-4-main-12.4.9-0.6.hum12026-09-04redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions)
  • every version up to 8.10.2+dfsg+~cs3.2.2-1: fixed in 8.10.2+dfsg+~cs3.2.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • 6.25.0 up to 6.28.1: fixed in 6.28.1
  • 7.28.0 up to 7.29.1: fixed in 7.29.1
  • 8.1.0 up to 8.10.2: fixed in 8.10.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 63× 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.

Showing the most recent 100 of 128 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 28 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-25 13:55 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-10-22 12:55 UTCEG score recompute
  8. 2026-10-22 12:55 UTCVendor advisory
  9. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-18 03:06 UTCEG score recompute
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-12 14:53 UTCEG score recompute
  21. 2026-10-11 19:18 UTCEG score recompute
  22. 2026-10-11 16:34 UTCEG score recompute
  23. 2026-10-11 13:52 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 75 more
  1. 2026-10-09 23:59 UTCEG score recompute
  2. 2026-10-09 23:59 UTCVendor advisory
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-09 01:11 UTCEG score recompute
  5. 2026-10-09 01:11 UTCVendor advisory
  6. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-07 23:53 UTCEG score recompute
  8. 2026-10-07 23:53 UTCVendor advisory
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-07 01:03 UTCEG score recompute
  11. 2026-10-07 01:03 UTCVendor advisory
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-06 01:37 UTCEG score recompute
  14. 2026-10-06 01:37 UTCVendor advisory
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-05 02:28 UTCEG score recompute
  17. 2026-10-05 02:28 UTCVendor advisory
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-04 03:39 UTCEG score recompute
  20. 2026-10-04 03:39 UTCVendor advisory
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-03 04:51 UTCEG score recompute
  23. 2026-10-03 04:51 UTCVendor advisory
  24. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-02 06:02 UTCEG score recompute
  26. 2026-10-02 06:02 UTCVendor advisory
  27. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-10-01 07:13 UTCEG score recompute
  29. 2026-10-01 07:13 UTCVendor advisory
  30. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-09-30 08:25 UTCEG score recompute
  32. 2026-09-30 08:25 UTCVendor advisory
  33. 2026-09-29 09:36 UTCEG score recompute
  34. 2026-09-29 09:36 UTCVendor advisory
  35. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-09-28 10:44 UTCEG score recompute
  37. 2026-09-28 10:44 UTCVendor advisory
  38. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  39. 2026-09-27 11:51 UTCEG score recompute
  40. 2026-09-27 11:51 UTCVendor advisory
  41. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  42. 2026-09-26 12:21 UTCEG score recompute
  43. 2026-09-26 12:21 UTCVendor advisory
  44. 2026-09-25 11:12 UTCEG score recompute
  45. 2026-09-25 11:12 UTCVendor advisory
  46. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  47. 2026-09-24 12:19 UTCEG score recompute
  48. 2026-09-24 12:19 UTCVendor advisory
  49. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-09-23 13:30 UTCEG score recompute
  51. 2026-09-23 13:30 UTCVendor advisory
  52. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-09-22 14:41 UTCEG score recompute
  54. 2026-09-22 14:41 UTCVendor advisory
  55. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-09-21 15:41 UTCEG score recompute
  57. 2026-09-21 15:41 UTCVendor advisory
  58. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-09-20 16:52 UTCVendor advisory
  60. 2026-09-19 18:03 UTCEG score recompute
  61. 2026-09-19 18:03 UTCVendor advisory
  62. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-09-18 19:12 UTCVendor advisory
  64. 2026-09-17 20:23 UTCEG score recompute
  65. 2026-09-17 20:23 UTCVendor advisory
  66. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  67. 2026-09-16 21:10 UTCEG score recompute
  68. 2026-09-16 21:10 UTCVendor advisory
  69. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-09-16 10:29 UTCEG score recompute
  71. 2026-09-16 10:29 UTCVendor advisory
  72. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  73. 2026-09-15 11:40 UTCEG score recompute
  74. 2026-09-15 11:40 UTCVendor advisory
  75. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile

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

Frequently asked(5)

What is CVE-2026-85024?
CVE-2026-85024 is a medium-severity vulnerability; its CVE record was published on September 4, 2026. undici bundles a WebSocket client whose permessage-deflate size-limit cleanup removes all listeners from the internal zlib inflate stream, including its error listener, while that stream can still emit. When a remote peer sends a compressed payload that crosses the built-in 128 MiB…
When was the CVE record for CVE-2026-85024 published?
The CVE record for CVE-2026-85024 was published on September 4, 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 September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-85024 actively exploited?
CVE-2026-85024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85024?
CVE-2026-85024 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85024?
A fix for CVE-2026-85024 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-85024 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-85024

Explore →

Is Your Infrastructure Affected by CVE-2026-85024?

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

Book a Demo →Browse All CVEs