Vulnerability in websocket-driver (CVE-2026-54464)
Summary
Vulnerability in websocket-driver (CVE-2026-54464). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.8.1 or later.
Original description
The description as published by the source.
Impact
If this library is used in tandem with the permessage-deflate extension, a
WebSocket server or client can be made to accept messages that are larger than
the configured maximum message size. This is because this limit is checked
against the message frames' length headers, which give the size of the
compressed data, not the size after decompression. This can lead to applications
accepting larger messages than expected and exceeding their intended resource
usage.
Patches
The issue has been patched in version 0.8.1, by checking the length of messages
after they are processed by incoming extensions. 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.
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-54464 has been found in websocket-driver.
Risk of unauthorized operations or information disclosure.
What to do: upgrade websocket-driver to 0.8.1 or later.
If unsure, ask your IT team or search "websocket-driver CVE-2026-54464" on the vendor's site.
CVE-2026-54464 (websocket-driver) — CWE-770
Patched: 0.8.1 — 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-770) exists in websocket-driver.
Check the vendor advisory for the affected versions of websocket-driver.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.8.1.
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.8.1ステージング環境で 0.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-54464 ruby-websocket-driver
- Ubuntu UBUNTU-CVE-2026-54464 ruby-websocket-driver
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com
- web cve.org
- web github.com