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 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, nvd
Elevated
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.7%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
50
EG Risk 50/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%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

Published

May 15, 2026

Last Modified

September 11, 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

Vendor Advisories for CVE-2026-45736(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatws2026-09-10redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17870615542026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17852301472026-08-04redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17846701012026-07-29redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-132026-07-29redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847137412026-07-28redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17847308572026-07-28redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17841449362026-07-21redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17841275532026-07-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatrhtas/rekor-search-ui-rhel9:17833271852026-07-09redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatdevspaces/dashboard-rhel9:17824987922026-07-08redhat
redhatansible-automation-platform-26/gateway-rhel9:17827615102026-07-01redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat
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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws7.4.2+~cs18.0.8-2 ... 8.8.1+~cs13.7.3-1 (17 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws8.11.0+~cs13.7.3-1 ... 8.21.3+~cs14.19.1-1 (10 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws8.18.1+~cs14.18.2-1 ... 8.21.3+~cs14.19.1-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-ws8.18.1+~cs14.18.2-1, 8.19.0+~cs14.19.1-1
  • every version up to 8.20.1+~cs14.19.1-1: fixed in 8.20.1+~cs14.19.1-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
ws—
  • 8.0.0 up to 8.20.1: fixed in 8.20.1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(8)

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 5× in last 7d / 33× 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 255 total refreshes for this CVE.

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

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

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 on May 15, 2026, with the most recent update on September 11, 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 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-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?
A fix for CVE-2026-45736 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45736 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-45736

Explore →

Is Your Infrastructure Affected by CVE-2026-45736?

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

Book a Demo →Browse All CVEs