websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, when websocket-driver is used to implement a WebSocket server on top of a TCP server using WebSocket::Driver.server() or to complement a WebSocket client, a peer can make a single connection consume an unbounded amount of memory by sending an HTTP request or response with a never-ending list of headers. This can lead to the receiving process running out of memory. This issue is fixed in version 0.8.1.
CVE-2026-54465
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- —
- EPSS
- 36.3%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 20, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026Memory exhaustion in HTTP header parser · Advisory · faye/websocket-driver-ruby · GitHub
Affected: version 0.8.1, by limiting the total size of HTTP
https://github.com/faye/websocket-driver-ruby/security/advisories/GHSA-8j3g-f24p-4mpwcommit 17b569f23289 (faye/websocket-driver-ruby)
Fix landed in faye/websocket-driver-ruby commit 17b569f23289 — awaiting tagged release
https://github.com/faye/websocket-driver-ruby/commit/17b569f232896e71d458404ccf4854f80e987710Vendor Advisories for CVE-2026-54465(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| websocket-driver | 0.1.0 ... 0.8.0 (32 versions) | 0.8.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:36 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 20:15 UTCEG score recompute▲ 6.30
- 2026-07-17 20:14 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
- 2026-07-15 22:19 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-54465?
When was CVE-2026-54465 disclosed?
Is CVE-2026-54465 actively exploited?
What is the CVSS score of CVE-2026-54465?
How do I remediate CVE-2026-54465?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54465
Is Your Infrastructure Affected by CVE-2026-54465?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.