Process crash via retained fragmented-message buffers
Published Jul 15, 2026 · Updated Jul 15, 2026
Resource exhaustion in WebSockets ws before 8.21.1 allows remote attackers to crash a Node.js process with fragmented messages. lib/receiver.js retains each incomplete fragment as a separate Buffer while the fragment-count guard permits a sequence just below maxFragments, so wrapper overhead exhausts the heap. The gate is an unauthenticated network peer that can keep fragmented WebSocket messages incomplete; the CNA later rejected this identifier as a duplicate of CVE-2026-48779.
Summary
What happened
Resource exhaustion in WebSockets ws before 8.21.1 allows remote attackers to crash a Node.js process with fragmented messages. lib/receiver.js retains each incomplete fragment as a separate Buffer while the fragment-count guard permits a sequence just below maxFragments, so wrapper overhead exhausts the heap. The gate is an unauthenticated network peer that can keep fragmented WebSocket messages incomplete; the CNA later rejected this identifier as a duplicate of CVE-2026-48779.
The record
- CVE
- CVE-2026-62389
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- WebSockets
- Product
- ws
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <8.21.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream tiny-fragment proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo