CVE-2026-18149

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.5% (41st 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-71617 (ENISA EUVD) · GHSA-pmjh-fq2x-6v4x (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.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici's retry handler can leave an already-exposed response body pending forever. When a server returns a successful response that declares a Content-Length, sends only part of the body, and closes the connection, the retry handler retries the request. If the retry returns a non-retryable status such as 400, the handler forwards that new response downstream and replaces its internal response stream, but the original response body that the application still holds is never ended or destroyed. As a result calls that read that body never settle, and the configured body timeout does not fire because its timer is tied to the connection parser rather than the orphaned body. An attacker-controlled server can trigger this with two short responses without keeping a connection open, and repeated requests accumulate pending promises and streams that can exhaust application concurrency or memory. This affects undici versions from 7.11.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.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.5%
EPSS %ILE
41st
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.5% within 30 daysSource: FIRST EPSS. 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 orphaned RetryHandler response body · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-pmjh-fq2x-6v4x

Vendor Advisories for CVE-2026-18149(5)

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.11.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(1)

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 100 of 122 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 22 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-18149?
CVE-2026-18149 is a medium-severity vulnerability; its CVE record was published on September 4, 2026. undici's retry handler can leave an already-exposed response body pending forever. When a server returns a successful response that declares a Content-Length, sends only part of the body, and closes the connection, the retry handler retries the request. If the retry returns a non-retryable status…
When was the CVE record for CVE-2026-18149 published?
The CVE record for CVE-2026-18149 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-18149 actively exploited?
CVE-2026-18149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18149?
CVE-2026-18149 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-18149?
A fix for CVE-2026-18149 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18149 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-18149

Explore →

Is Your Infrastructure Affected by CVE-2026-18149?

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

Book a Demo →Browse All CVEs