CVE-2026-84933

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3% (22nd 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

Also known asEUVD-2026-71518 (ENISA EUVD) · GHSA-2jfj-6hjv-fm6j (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
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: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici's cache interceptor does not handle the Set-Cookie response header anywhere in its cache path, so it neither refuses to store nor strips that header. In shared cache mode, which is the default, an otherwise cacheable response that carries a Set-Cookie header, for example one marked with a public and max-age directive, is stored and then re-served to a later caller that matches the same cache key. As a result one caller's cookie is disclosed to a different caller, and an untrusted server can inject cookies into cached responses served to all subsequent callers. This violates the requirement that a shared cache must not store cookies. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 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
22nd
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 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-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 15, 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-user cookie disclosure via Set-Cookie caching in shared caches · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-2jfj-6hjv-fm6j

Vendor Advisories for CVE-2026-84933(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
redhatgrafana12-4-main-12.4.10-0.2.hum12026-09-09redhat
redhatnodejs26-main-26.7.0-1.5.2.hum12026-08-12redhat
redhatnodejs24-main-24.18.1-0.2.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—
  • 7.0.0 up to 7.29.1: fixed in 7.29.1
  • 8.0.0 up to 8.10.2: fixed in 8.10.2
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-84933?
CVE-2026-84933 is a high-severity vulnerability; its CVE record was published on September 4, 2026. undici's cache interceptor does not handle the Set-Cookie response header anywhere in its cache path, so it neither refuses to store nor strips that header. In shared cache mode, which is the default, an otherwise cacheable response that carries a Set-Cookie header, for example one marked with a…
When was the CVE record for CVE-2026-84933 published?
The CVE record for CVE-2026-84933 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-84933 actively exploited?
CVE-2026-84933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84933?
CVE-2026-84933 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-84933?
A fix for CVE-2026-84933 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84933 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-84933

Explore →

Is Your Infrastructure Affected by CVE-2026-84933?

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

Book a Demo →Browse All CVEs