CVE-2026-48779

ws: Memory exhaustion DoS from tiny fragments and data chunks

HIGH
7.5
CVSS Score
Published: June 16, 2026 at 09:26 PM UTC
Updated: September 11, 2026 at 01:50 PM UTC
17 products affected across 3 vendorsWsEnterprise LinuxOpenShift Container Platform

Using ws by websockets?

Get instant alerts when new vulnerabilities affect ws - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.8%
SSVC
PoC

Description

ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.1.0 ≤ v < 5.2.56.0.0 ≤ v < 6.2.47.0.0 ≤ v < 7.5.118.0.0 ≤ v < 8.21.0
Affected range stops below 5.2.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.21.0, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 2 (unaffected)
Vendor states this is fixed in 0:1.1.2-1.el10_2 (unaffected)
Vendor states this is fixed in 10 (unaffected)
Vendor states this is fixed in 8 (unaffected)
Vendor states this is fixed in 9 (unaffected)
All versions
Vendor states this is fixed in 1786611759 (unaffected)
Vendor states this is fixed in 1787121387 (unaffected)
Vendor states this is fixed in 1787250508 (unaffected)
Vendor states this is fixed in 1787250617 (unaffected)
Vendor states this is fixed in 1787251250 (unaffected)
Vendor states this is fixed in 1787251550 (unaffected)
Vendor states this is fixed in 1787347991 (unaffected)
Vendor states this is fixed in 1787801527 (unaffected)

References (34)

x_refsource_CONFIRMExploitMitigationPatchVendor Advisory
Source: cverecord
https://github.com/websockets/ws/security/advisories/GHSA-96hv-2xvq-fx4p
Vendor Advisoryx_refsource_REDHAT
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:29197
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:33155
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:33160

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400CWE-770CWE-1050

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card