Vulnerability in websocket-driver (CVE-2026-54466)
Summary
Vulnerability in websocket-driver (CVE-2026-54466). Data can be tampered with by attackers. Mitigation: upgrade to 0.7.5 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54466 has been found in websocket-driver.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade websocket-driver to 0.7.5 or later.
If unsure, ask your IT team or search "websocket-driver CVE-2026-54466" on the vendor's site.
CVE-2026-54466 (websocket-driver) — CWE-130 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.7.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-130) exists in websocket-driver.
Check the vendor advisory for the affected versions of websocket-driver.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to 0.7.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'websocket-driver' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'websocket-driver' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
websocket-driverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade websocket-driver to 0.7.5ステージング環境で 0.7.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-54466 node-websocket-driver
- Ubuntu UBUNTU-CVE-2026-54466 node-websocket-driver
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com
- web github.com