This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as a duplicate of CVE-2026-48779.
No vendor fix or workaround currently provided.
OpenCVE Recommended Actions
- Upgrade websockets:ws to version 8.21.1 or later, which corrects the fragment guard logic and eliminates the ability to create unbounded fragments.
- If an upgrade is not immediately possible, configure the library to set maxFragments to a low number (e.g., 1) or disable fragmentation entirely, thereby preventing accumulation of uncompleted fragments.
- Implement application‑level throttling or rate limiting on incoming WebSocket connections and fragment streams to constrain the rate of message processing, reducing the impact of any attempted memory exhaustion attack.
- Deploy monitoring of Node.js heap usage and set alerts for anomalous memory growth, ensuring rapid detection if an attacker is successfully exhausting resources.
Generated by OpenCVE AI on July 31, 2026 at 03:14 UTC.
Tracking
Sign in to view the affected projects.
No advisories yet.
No reference.
Wed, 29 Jul 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | ws < 8.21.1 Default maxFragments Allows Memory Exhaustion DoS | |
| Metrics |
ssvc
|
Wed, 29 Jul 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ws before 8.21.1 contains a memory exhaustion vulnerability in lib/receiver.js where the fragment guard only triggers when fragment count reaches maxFragments, allowing attackers to exhaust memory by sending incomplete fragmented WebSocket messages. Attackers can send a text frame with FIN=0 followed by continuation frames without completing the sequence, causing each fragment to be stored as a separate Buffer object with significant overhead, enabling denial of service through heap exhaustion. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as a duplicate of CVE-2026-48779. |
| Weaknesses | CWE-770 | |
| CPEs | ||
| Vendors & Products |
Websockets Project
Websockets Project websockets |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Tue, 28 Jul 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Websockets Project
Websockets Project websockets |
|
| CPEs | cpe:2.3:a:websockets_project:websockets:*:*:*:*:*:python:*:* | |
| Vendors & Products |
Websockets Project
Websockets Project websockets |
Thu, 16 Jul 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Websockets
Websockets ws |
|
| Vendors & Products |
Websockets
Websockets ws |
Wed, 15 Jul 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 15 Jul 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ws before 8.21.1 contains a memory exhaustion vulnerability in lib/receiver.js where the fragment guard only triggers when fragment count reaches maxFragments, allowing attackers to exhaust memory by sending incomplete fragmented WebSocket messages. Attackers can send a text frame with FIN=0 followed by continuation frames without completing the sequence, causing each fragment to be stored as a separate Buffer object with significant overhead, enabling denial of service through heap exhaustion. | |
| Title | ws < 8.21.1 Default maxFragments Allows Memory Exhaustion DoS | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: REJECTED
Assigner: VulnCheck
Published:
Updated: 2026-07-29T17:23:48.982Z
Reserved: 2026-07-13T22:40:54.412Z
Link: CVE-2026-62389
Updated:
Status : Rejected
Published: 2026-07-15T18:16:49.893
Modified: 2026-07-29T18:16:57.713
Link: CVE-2026-62389
No data.
OpenCVE Enrichment
Updated: 2026-07-31T03:15:04Z
No weakness.