GitHub Advisoryadvisory · npm

GHSA-xv26-6w52-cph6 websocket-driver: Message corruption via abuse of protocol length headers

CRITICAL Published 2026-07-15 Modified 2026-07-15 Official page ↗
Aliases
CVE-2026-54466
Ecosystem
npm
Packages
websocket-driver
Severity
Critical
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
Weaknesses
CWE-130
Reviewed
2026-07-15

Affected packages

• npm websocket-driver: < 0.7.5 → fixed in 0.7.5

Description

Impact The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a client can make the server parse these bytes into an ever-growing integer. Since JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. Patches The issue has been patched in version 0.7.5 by rejecting the message if the length header exceeds the configured maximum message length. All users should upgrade to this version. Workarounds No known workarounds exist. Acknowledgements This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.

Related

Alias · CVE (1)

  • CVE-2026-54466 websocket-driver is a WebSocket protocol handler with pluggable I/O. vulnerability

Weakness · CWE (1)

  • CWE-130 Improper Handling of Length Parameter Inconsistency weakness

References