Answer in brief
CVE-2026-48779 records a High severity (CVSS 7.5) vulnerability in ws: Memory exhaustion DoS from tiny fragments and data chunks. The current sources do not mark it as known exploited. The current feed maps websockets/ws (generic), ws (npm), ws (npm), ws (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps websockets/ws (generic), ws (npm), ws (npm), ws (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:ws_project:ws:*:*:*:*:*:node.js:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| websockets/wsgeneric | >= 1.1.0, < 5.2.5 || >= 6.0.0, < 6.2.4 || >= 7.0.0, < 7.5.11 || >= 8.0.0, < 8.21.0 | Not reported |
| wsnpm | >=1.1.0,<5.2.5 | 5.2.5 |
| wsnpm | >=6.0.0,<6.2.4 | 6.2.4 |
| wsnpm | >=7.0.0,<7.5.11 | 7.5.11 |
| wsnpm | >=8.0.0,<8.21.0 | 8.21.0 |
Published upstream
Jun 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.