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.
Security readout for executives and security teams
Plain-English summary
This flaw can let a remote, unauthenticated actor cause ws to disclose memory contents during WebSocket close handling. The known affected package is the Node.js ws library before 8.20.1. Business urgency is high where ws is internet-facing or embedded in products handling sensitive data.
Executive priority
Treat as high priority for externally reachable Node.js services because the impact is data exposure, not service disruption. Patch quickly, but avoid claiming emergency exploitation unless new evidence appears outside this bundle.
Technical view
CVE-2026-45736 affects ws >=8.0.0 and <8.20.1. websocket.close() can disclose uninitialized memory when a TypedArray is passed as the reason argument. The issue maps to CWE-824 and CWE-908 and has CVSS 7.5 for network-reachable confidentiality impact only.
Likely exposure
Exposure is likely in Node.js services, frameworks, or bundled products using ws versions 8.0.0 through 8.20.0. The bundle does not identify other affected products beyond websockets/ws and listed Red Hat advisories.
Exploitation context
The CVSS vector indicates remote, low-complexity, unauthenticated exploitation with no user interaction. The bundle marks KEV false and provides no evidence of active exploitation, public exploit code, or weaponized campaigns.
Researcher notes
The vulnerable condition is specifically TypedArray handling in websocket.close() reason processing. Analysis should focus on dependency reachability and whether application-controlled input can influence close reasons. Do not broaden affected scope beyond ws without vendor evidence.
Mitigation direction
Upgrade ws to version 8.20.1 or later.
Identify transitive dependencies that bundle vulnerable ws versions.
Apply relevant Red Hat errata where Red Hat packages embed ws.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-824: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-824 · source CWE mapping
Access of Uninitialized Pointer
Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.