CVE-2026-54466 json
websocket-driver: Message corruption via abuse of protocol length headers
published 5mo ago modified 18d ago also EUVD-2026-45335 , GHSA-xv26-6w52-cph6
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm websocket-driver 0.7.5
- faye websocket-driver 0.7.5
- node-websocket-driver Debian 14 0.7.5+~cs0.6.14-1
debian advisories DEBIAN-CVE-2026-54466
- agama-web-ui openSUSE Tumbleweed 24+0.a836cced5-52.1
- agama-web-ui openSUSE Leap 16.0 17+673.b97ba64d6-160000.12.1
opensuse advisories openSUSE-SU-2026:11680-1openSUSE-SU-2026:21448-1
Is CVE-2026-54466 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.2 | 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 |
| CNA | 4.0 | 9.2 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | websocket-driver | <0.7.5 |
0.7.5 |
Affected products
- faye websocket-driver-node
Classification
- Weakness
-
- CWE-130 Improper Handling of Length Parameter Inconsistency
References
-
github.com
/faye/websocket-driver-node/commit/5b197ca874dab58e96cacad8a3c256797d804680
patch
-
github.com
/faye/websocket-driver-node/security/advisories/GHSA-xv26-6w52-cph6
web, vendor-advisory, advisory
-
github.com
/faye/websocket-driver-node
package
-
github.com
/faye/websocket-driver-node/releases/tag/0.7.5
web
Sources
- CVE List CVE-2026-54466
- GitHub Advisory GHSA-xv26-6w52-cph6
- NVD CVE-2026-54466
- Maintainer advisory GHSA-xv26-6w52-cph6
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of faye/websocket-driver-node published their own advisory on GitHub. Reviewed sources take precedence over it.