CVE-2026-54466: websocket-driver: Message corruption via abuse of protocol length headers

Published Jul 15, 2026
·
Updated

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.

Other sources

websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, 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 in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.

— MITRE

Affected Software

3 affected componentsFixes available
npm/websocket-driver<0.7.5
0.7.5
Faye Websocket-driver Ruby<0.7.5
IBM Concert Software<=1.0-3.0.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/websocket-driver to a version that resolves this vulnerability.

    Fixed in 0.7.5
  2. Upgrade

    Upgrade websocket-driver to a version that resolves this vulnerability.

    Fixed in 0.7.5

Event History

Jul 15, 2026
Advisory Published
via GitHub·10:07 PM
Data Sourced
via GitHub·10:07 PM
DescriptionWeaknessAffected Software
Jul 17, 2026
CVE Published
via MITRE·08:53 PM
Data Sourced
via MITRE·08:53 PM
DescriptionWeakness
Data Sourced
via NVD·09:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 29, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-54466?

CVE-2026-54466 has a critical severity rating of 9.2.

2

How does CVE-2026-54466 impact WebSocket communications?

CVE-2026-54466 allows message corruption via abuse of protocol length headers, potentially impacting server-client communication.

3

What software is affected by CVE-2026-54466?

CVE-2026-54466 affects the npm package websocket-driver.

4

How can I mitigate CVE-2026-54466?

To mitigate CVE-2026-54466, update to a patched version of the websocket-driver package.

5

What is the nature of the vulnerability in CVE-2026-54466?

CVE-2026-54466 involves exploiting length header encoding in the WebSocket protocol to corrupt messages.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203