CVE-2026-45736

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 63% 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
Elevated
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 4.4Exploit: NoneExposed: 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
4.4
EG Score
4.4(medium)
EPSS
49.3%
KEV
Not listed

Published

May 15, 2026

Last Modified

July 3, 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(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatdotnet9-0-main-9.0.118-1.hum12026-06-19redhat
redhatdotnet8-0-main-8.0.128-1.hum12026-06-18redhat
redhatdotnet10-0-main-10.0.109-1.hum12026-06-17redhat
redhatyarnpkg-main-1.22.22-18.1.hum12026-04-11redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
ws8.20.1

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 59× 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.

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

Frequently asked(5)

What is CVE-2026-45736?
CVE-2026-45736 is a medium 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 July 3, 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 49.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45736?
CVE-2026-45736 has a CVSS v4.0 base score of 4.4 (CNA self-assessment; NVD's own analysis pending).
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.