Skip to main content
VulnerabilityPublished Updated

CVE-2026-48779: websockets ws · Uncontrolled Resource Consumption

Affects websockets wsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 8.21.0 : patch websockets ws soon.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.21.0, 7.5.11, 6.2.4 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade websockets ws to 8.21.0, 7.5.11, 6.2.4 or 5.2.5.

Affected software

ProductAffectedFixed in
websocketswsAffected
  • >=8.0.0 <8.21.0
Fixed in
  • 8.21.0
websocketswsAffected
  • >=7.0.0 <7.5.11
Fixed in
  • 7.5.11
websocketswsAffected
  • >=6.0.0 <6.2.4
Fixed in
  • 6.2.4
websocketswsAffected
  • >=1.1.0 <5.2.5
Fixed in
  • 5.2.5
npmwspkg:npm/wsOther threatsAffected
  • >=1.1.0 <5.2.5
  • >=6.0.0 <6.2.4
  • >=7.0.0 <7.5.11
  • >=8.0.0 <8.21.0
Fixed in
  • 5.2.5
  • 6.2.4
  • 7.5.11
  • 8.21.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in ws versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0. Users should upgrade to these or later versions to remediate the vulnerability. Red Hat advisories indicate that no effective mitigation other than upgrading currently meets their criteria for ease of use, applicability, and stability. Therefore, upgrading is the recommended remediation.

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.

References

Community reviews

Loading reviews…