CVE-2026-12151

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service.

Affected applications are those using the undici WebSocket client (new WebSocket(...)) or the WebSocketStream API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint.

All releases starting at undici 6.17.0 are affected.

Patches: Upgrade to undici >= 6.26.0, >= 7.28.0, or >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

June 17, 2026

Last Modified

August 19, 2026

Advisory Details (2)

Auto-updated Jun 17, 2026
Patch available. Sources: github.
github Patch Available

undici WebSocket client vulnerable to denial of service via fragment count bypass · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-vxpw-j846-p89q
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

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

Patch Availability(21)

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 rangeFixed inDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (39 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 7.3.0+dfsg1+~cs24.12.11-2 (11 versions)8.5.0+dfsg+~cs3.2.0-1
npm(1)
PackageVulnerable rangeFixed inDependents
undici8.5.0

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 29× in last 7d / 112× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-12151?
CVE-2026-12151 is a high vulnerability published on June 17, 2026. Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size…
When was CVE-2026-12151 disclosed?
CVE-2026-12151 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12151 actively exploited?
CVE-2026-12151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.6% of all scored CVEs.
What is the CVSS score of CVE-2026-12151?
CVE-2026-12151 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-12151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12151

Explore →

Is Your Infrastructure Affected by CVE-2026-12151?

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