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 has been withdrawn by MITRE
MITRE marked CVE-2026-62389 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as a duplicate of CVE-2026-48779.
CVE-2026-62389
✕ Withdrawn — historical dataHIGHPre-NVD 7.5
7.5CVSS
- CVSS v3
- 7.5
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
July 15, 2026
Last Modified
July 28, 2026
Frequently asked(4)
What is CVE-2026-62389?
CVE-2026-62389 is a rejected CVE ID: its record was withdrawn on July 29, 2026 and no longer describes a vulnerability. Reason given: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as a duplicate of CVE-2026-48779. Its record names CVE-2026-48779 as the replacement.
When was the CVE record for CVE-2026-62389 published?
The CVE record for CVE-2026-62389 was published on July 15, 2026. EchelonGraph's copy of the record carries a last-modified date of July 28, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-62389?
CVE-2026-62389 has a CVSS base score of 7.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-62389?
There is nothing to remediate under CVE-2026-62389: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability. Its record names CVE-2026-48779 as the replacement; act on that CVE instead.