CVE-2026-54466
websocket-driver parsing bug lets crafted frames corrupt payload parsing.
Is CVE-2026-54466 being exploited?
Not confirmed. CVE-2026-54466 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-54466?
CVE-2026-54466 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54466?
Yes. A fix has been recorded for CVE-2026-54466. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54466 affect?
CVE-2026-54466 affects websocket-driver < 0.7.5, Node.js applications using websocket-driver, Servers accepting draft-75 WebSocket frames. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54466?
Upgrade to websocket-driver v0.7.5+ and block draft-75 frames at the edge.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can send crafted draft75 WebSocket frames causing integer precision loss and payload misparsing, enabling DoS or data corruption.
Patch when possible
- affected< 0.7.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.