CVE-2026-2229

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 43% 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: cna:openjs, epss
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ImpactThe undici WebSocket client is vulnerable to a denial-of-service attack due to improper validation of the server_max_window_bits parameter in the permessage-deflate extension. When a WebSocket client connects to a server, it automatically advertises support for permessage-deflate compression. A malicious server can respond with an out-of-range server_max_window_bits value (outside zlib's valid range of 8-15). When the server subsequently sends a compressed frame, the client attempts to create a zlib InflateRaw instance with the invalid windowBits value, causing a synchronous RangeError exception that is not caught, resulting in immediate process termination.

The vulnerability exists because:

* The isValidClientWindowBits() function only validates that the value contains ASCII digits, not that it falls within the valid range 8-15 * The createInflateRaw() call is not wrapped in a try-catch block * The resulting exception propagates up through the call stack and crashes the Node.js process

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

Published

March 12, 2026

Last Modified

September 14, 2026

Advisory Details (9)

Auto-updated Jul 6, 2026
Patch available. Sources: github, redhat.
generic

Zlib | Node.js v26.4.0 Documentation

https://nodejs.org/api/zlib.html#class-zlibinflateraw
github Patch Available

Unhandled Exception in undici WebSocket Client Due to Invalid server_max_window_bits Validation · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-v9p9-hfj2-hcw8
generic

RFC 7692 - Compression Extensions for WebSocket

https://datatracker.ietf.org/doc/html/rfc7692
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-pf6-rhel9:17828399962026-07-01redhat
redhatopenshift-pipelines/pipelines-console-plugin-rhel9:17799102012026-05-29redhat
redhatdevspaces/code-rhel9:17798145922026-05-28redhat
redhatcryostat/cryostat-rhel9:4.2.0-92026-05-26redhat
redhatrhdh/rhdh-hub-rhel9:17779032622026-05-05redhat
redhatrhdh/rhdh-hub-rhel9:17767842862026-04-22redhat
redhatnodejs:22-9060020260409121057.rhel92026-04-14redhat
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs:24-8100020260408131901.6d8804032026-04-13redhat
redhatnodejs22-1:22.22.2-2.el10_02026-04-09redhat
redhatnodejs:22-9070020260401095228.rhel92026-04-09redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat
redhatnodejs22-1:22.22.2-1.el10_12026-04-08redhat
redhatnodejs:22-8100020260331102257.6d8804032026-04-08redhat
redhatrhoai/odh-dashboard-rhel8:17742821362026-03-25redhat

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 ... 7.3.0+dfsg1+~cs24.12.11-2 (7 versions)
  • every version up to 7.24.5+dfsg+~cs3.2.0-1: fixed in 7.24.5+dfsg+~cs3.2.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • every version up to 6.24.0: fixed in 6.24.0
  • 7.0.0 up to 7.24.0: fixed in 7.24.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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 154 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-2229?
CVE-2026-2229 is a high vulnerability published on March 12, 2026. ImpactThe undici WebSocket client is vulnerable to a denial-of-service attack due to improper validation of the servermaxwindowbits parameter in the permessage-deflate extension. When a WebSocket client connects to a server, it automatically advertises support for permessage-deflate compression. A…
When was CVE-2026-2229 disclosed?
CVE-2026-2229 was first published on March 12, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2229 actively exploited?
CVE-2026-2229 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-2229?
CVE-2026-2229 has a CVSS base score of 7.5 (the CNA's own assessment, by openjs; NVD's own analysis pending).
How do I remediate CVE-2026-2229?
A fix for CVE-2026-2229 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2229 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-2229

Explore →

Is Your Infrastructure Affected by CVE-2026-2229?

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