No data.
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
No reference.
| Type | Values Removed | Values Added |
|---|---|---|
| Title | ws < 8.21.1 Default maxFragments Allows Memory Exhaustion DoS | |
| Metrics |
ssvc
|
| 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
|
| 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 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Websockets
Websockets ws |
|
| Vendors & Products |
Websockets
Websockets ws |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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
|
No weakness.