CVE-2026-45736

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 48% 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, nvd
Trending — Patch released this weekElevated
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: Elevated riskExposed: 0

A fix is available — apply it.

ws is an open source WebSocket client and server for Node.js. Prior to 8.20.1, the websocket.close() implementation is vulnerable to uninitialized memory disclosure when a TypedArray is passed as the reason argument. This vulnerability is fixed in 8.20.1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

May 15, 2026

Last Modified

August 20, 2026

Advisory Details (2)

Auto-updated May 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Uninitialized memory disclosure · Advisory · websockets/ws · GitHub

https://github.com/websockets/ws/security/advisories/GHSA-58qx-3vcg-4xpx
generic

[security] Fix uninitialized memory disclosure in `websocket.close()` · websockets/ws@c0327ec · GitHub

https://github.com/websockets/ws/commit/c0327ec15a54d701eb6ccefaa8bef328cfc03086

Patch Availability(22)

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-ws7.4.2+~cs18.0.8-2 ... 8.8.1+~cs13.7.3-1 (17 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-ws8.11.0+~cs13.7.3-1 ... 8.21.1+~cs14.19.1-1 (9 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ws8.18.1+~cs14.18.2-1, 8.19.0+~cs14.19.1-1, 8.20.1+~cs14.19.1-1, 8.21.0+~cs14.19.1-1, 8.21.1+~cs14.19.1-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ws8.18.1+~cs14.18.2-1, 8.19.0+~cs14.19.1-18.20.1+~cs14.19.1-1
npm(1)
PackageVulnerable rangeFixed inDependents
ws8.20.1

Weakness Classification(2)

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

Additional Vendor Advisories

(3)

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 24× in last 7d / 95× 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 189 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45736?
CVE-2026-45736 is a high vulnerability published on May 15, 2026. ws is an open source WebSocket client and server for Node.js. Prior to 8.20.1, the websocket.close() implementation is vulnerable to uninitialized memory disclosure when a TypedArray is passed as the reason argument. This vulnerability is fixed in 8.20.1.
When was CVE-2026-45736 disclosed?
CVE-2026-45736 was first published in the National Vulnerability Database on May 15, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45736 actively exploited?
CVE-2026-45736 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 48.0% of all scored CVEs.
What is the CVSS score of CVE-2026-45736?
CVE-2026-45736 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45736?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45736, 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-45736

Explore →

Is Your Infrastructure Affected by CVE-2026-45736?

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