CVE-2026-85152

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th 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

Also known asEUVD-2026-71474 (ENISA EUVD) · GHSA-vp8m-p9jh-q5pm (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
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.2%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici 8.10.0 omits the destination origin from the cache and request-deduplication keys when the cache or deduplicate interceptor is composed directly onto a Client or Pool. Because the internal cache key falls back to an empty origin string, a cacheable or in-flight response from one upstream origin is returned for a request to a different, trusted origin whenever the method, path, and relevant headers match, which permits cross-origin information disclosure and persistent cache poisoning. The reporter demonstrated a full authentication bypass in which a JWT signed with an attacker-controlled key was accepted as belonging to a trusted issuer, and the trusted origin was never contacted. This is a regression introduced in 8.10.0 and affects undici versions from 8.10.0 up to 8.10.2. Applications using an Agent, which carries the origin in its dispatch options, are not affected. Users should upgrade to undici 8.10.2.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
5th
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.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-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.2% 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 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 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

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 cross-origin cache poisoning via missing origin isolation in interceptors · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-vp8m-p9jh-q5pm

Vendor Advisories for CVE-2026-85152(12)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17917882672026-10-19redhat
redhatansible-automation-platform/automation-portal:17912953792026-10-12redhat
redhatansible-automation-platform/automation-portal:17912937802026-10-12redhat
redhatnodejs:24-9080020260921144317.rhel92026-09-30redhat
redhatnodejs:24-8100020260921144227.6d8804032026-09-30redhat
redhatnodejs24-1:24.21.0-1.el10_22026-09-29redhat
redhatgrafana12-4-main-12.4.9-0.6.hum12026-09-04redhat
redhatnodejs24-main-24.18.1-0.2.2.hum12026-08-12redhat
redhatnodejs26-main-26.7.0-1.5.2.hum12026-08-12redhat

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

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

Frequently asked(5)

What is CVE-2026-85152?
CVE-2026-85152 is a high-severity vulnerability; its CVE record was published on September 4, 2026. undici 8.10.0 omits the destination origin from the cache and request-deduplication keys when the cache or deduplicate interceptor is composed directly onto a Client or Pool. Because the internal cache key falls back to an empty origin string, a cacheable or in-flight response from one upstream…
When was the CVE record for CVE-2026-85152 published?
The CVE record for CVE-2026-85152 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-85152 actively exploited?
CVE-2026-85152 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85152?
CVE-2026-85152 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85152?
A fix for CVE-2026-85152 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-85152 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-85152

Explore →

Is Your Infrastructure Affected by CVE-2026-85152?

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

Book a Demo →Browse All CVEs