CVE-2026-84947

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (9th 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-71517 (ENISA EUVD) · GHSA-2gqq-gqf2-x968 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.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
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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 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.2%
EPSS %ILE
9th
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.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-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.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 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 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

undici vulnerable to response truncation via oversized chunked responses in the dump interceptor · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-2gqq-gqf2-x968
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

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

Vendor Advisories for CVE-2026-84947(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
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—
  • 7.1.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 10× in last 7d / 62× 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 99 of 116 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 17 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% · 9th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-25 13:55 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-22 12:56 UTCEG score recompute
  8. 2026-10-22 12:56 UTCVendor advisory
  9. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-18 03:06 UTCEG score recompute
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-12 14:53 UTCEG score recompute
  20. 2026-10-11 19:18 UTCEG score recompute
  21. 2026-10-11 16:34 UTCEG score recompute
  22. 2026-10-11 13:52 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-09 23:06 UTCEG score recompute
Show 74 more
  1. 2026-10-09 23:06 UTCVendor advisory
  2. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-09 01:10 UTCEG score recompute
  4. 2026-10-09 01:10 UTCVendor advisory
  5. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-07 23:05 UTCVendor advisory
  8. 2026-10-06 18:20 UTCEG score recompute
  9. 2026-10-06 18:20 UTCVendor advisory
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-05 20:32 UTCEG score recompute
  12. 2026-10-05 20:32 UTCVendor advisory
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-04 22:44 UTCVendor advisory
  16. 2026-10-04 00:56 UTCEG score recompute
  17. 2026-10-04 00:56 UTCVendor advisory
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-03 01:30 UTCEG score recompute
  20. 2026-10-03 01:30 UTCVendor advisory
  21. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-02 03:38 UTCEG score recompute
  23. 2026-10-02 03:38 UTCVendor advisory
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-01 04:24 UTCEG score recompute
  26. 2026-10-01 04:24 UTCVendor advisory
  27. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-30 06:35 UTCEG score recompute
  29. 2026-09-30 06:35 UTCVendor advisory
  30. 2026-09-29 08:46 UTCEG score recompute
  31. 2026-09-29 08:46 UTCVendor advisory
  32. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-09-28 10:57 UTCEG score recompute
  34. 2026-09-28 10:57 UTCVendor advisory
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-27 13:09 UTCEG score recompute
  37. 2026-09-27 13:09 UTCVendor advisory
  38. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-26 15:20 UTCEG score recompute
  40. 2026-09-26 15:20 UTCVendor advisory
  41. 2026-09-25 16:14 UTCVendor advisory
  42. 2026-09-24 18:24 UTCEG score recompute
  43. 2026-09-24 18:24 UTCVendor advisory
  44. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-09-23 19:45 UTCEG score recompute
  46. 2026-09-23 19:45 UTCVendor advisory
  47. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-09-22 21:05 UTCEG score recompute
  49. 2026-09-22 21:05 UTCVendor advisory
  50. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  51. 2026-09-21 23:17 UTCEG score recompute
  52. 2026-09-21 23:17 UTCVendor advisory
  53. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  54. 2026-09-21 01:29 UTCEG score recompute
  55. 2026-09-21 01:29 UTCVendor advisory
  56. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  57. 2026-09-20 03:38 UTCEG score recompute
  58. 2026-09-20 03:38 UTCVendor advisory
  59. 2026-09-19 05:49 UTCEG score recompute
  60. 2026-09-19 05:49 UTCVendor advisory
  61. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  62. 2026-09-18 08:01 UTCEG score recompute
  63. 2026-09-18 08:01 UTCVendor advisory
  64. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-09-17 10:13 UTCEG score recompute
  66. 2026-09-17 10:13 UTCVendor advisory
  67. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  68. 2026-09-16 12:25 UTCEG score recompute
  69. 2026-09-16 12:25 UTCVendor advisory
  70. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  71. 2026-09-15 14:36 UTCEG score recompute▲ 1.60
  72. 2026-09-15 14:36 UTCVendor advisory
  73. 2026-09-15 14:31 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile

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

Frequently asked(5)

What is CVE-2026-84947?
CVE-2026-84947 is a medium-severity vulnerability; its CVE record was published on September 4, 2026. undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion…
When was the CVE record for CVE-2026-84947 published?
The CVE record for CVE-2026-84947 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-84947 actively exploited?
CVE-2026-84947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84947?
CVE-2026-84947 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-84947?
A fix for CVE-2026-84947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84947 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-84947

Explore →

Is Your Infrastructure Affected by CVE-2026-84947?

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

Book a Demo →Browse All CVEs