CVE-2026-54465

websocket-driver: Memory exhaustion in HTTP header parser

Published Jul 17, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-8j3g-f24p-4mpw websocket-driver: Memory exhaustion in HTTP header parser
History
Type Values Removed Values Added
First Time appeared Faye
Faye websocket-driver-ruby
Vendors & Products Faye
Faye websocket-driver-ruby
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title websocket-driver: Memory exhaustion in HTTP header parser
Weaknesses CWE-770
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 20, 2026, 1:49 PM
Reserved
Jun 15, 2026, 3:30 PM
Status
Analyzed
Published
Jul 17, 2026, 8:17 PM
Modified
Oct 24, 2026, 8:10 PM