PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-45736 websockets CVE debrief

A vulnerability in the ws WebSocket client and server for Node.js could allow for uninitialized memory disclosure when a TypedArray is passed as the reason argument to the websocket.close() implementation. The CVE record was published on 2026-05-15T15:16:54.103Z and has not been modified since then. The NVD entry is currently Modified. Defenders responsible for Node.js environments using the ws library, especially those handling untrusted input, should assess exposure and apply patches or mitigations as necessary. This vulnerability is fixed in version 8.20.1.

Vendor
websockets
Product
ws
CVSS
MEDIUM 4.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-15
Original CVE updated
2026-09-11
Advisory published
2026-05-15
Advisory updated
2026-09-11

Who should care

Defenders responsible for Node.js environments using the ws library, especially those handling untrusted input, should assess exposure and apply patches or mitigations as necessary.

Why it matters

CVE-2026-45736 is a vulnerability in the ws WebSocket client and server for Node.js that could allow for uninitialized memory disclosure. Defenders should prioritize verifying exposure in Node.js environments, especially where untrusted input is handled, and apply patches or mitigations as necessary.

  • Potential information disclosure due to uninitialized memory exposure
  • Verification of exposure in Node.js environments using the ws library
  • Application of patches or mitigations to prevent exploitation
  • Monitoring for potential exploitation attempts

Technical summary

The ws WebSocket client and server for Node.js is vulnerable to uninitialized memory disclosure when a TypedArray is passed as the reason argument to the websocket.close() implementation. This vulnerability is fixed in version 8.20.1. Defenders should prioritize verifying exposure in Node.js environments using the ws library, especially where untrusted input is handled. Assess the risk of potential information disclosure and apply patches or mitigations as necessary. The vulnerability allows for potential information disclosure due to uninitialized memory exposure.

Defensive priority

Defenders should prioritize verifying exposure in Node.js environments using the ws library, especially where untrusted input is handled. Assess the risk of potential information disclosure and apply patches or mitigations as necessary.

Recommended defensive actions

  • Verify if Node.js environments using the ws library are exposed to untrusted input
  • Assess the risk of potential information disclosure
  • Apply patches or mitigations as necessary
  • Monitor for potential exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but specific exploitation details are limited. The vendor has provided a patch in version 8.20.1. Defenders should verify if Node.js environments using the ws library are exposed to untrusted input, assess the risk of potential information disclosure, and apply patches or mitigations as necessary. Evidence is limited, and defenders should exercise caution when verifying exposure.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-45736 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-45736

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-45736 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45736

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

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

    [email protected] - Patch

  • Source reference

    Unverified legacy reference

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

    [email protected] - Exploit, Patch, Vendor Advisory

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:26638

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:26994

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:27171

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:29197

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:33574

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:34374

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.