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.

Analysis

AI-generated

Technical impact

The websocket‑driver Ruby implementation parses HTTP headers during the WebSocket handshake without an upper bound on the total header size or list of headers. Because the parser allocates memory for each header entry, an attacker can cause the application process to consume an unbounded amount of memory, eventually exhausting available system RAM and forcing the process to crash or become unresponsive. This flaw is a classic example of CWE‑770: Excessive Resource Consumption.

Affected Systems

The vulnerability impacts versions of faye::websocket-driver‑ruby prior to 0.8.1 that are used to build WebSocket servers over TCP or to augment WebSocket clients. Any deployment that relies on a pre‑0.8.1 release of this library and exposes a public or network reachable TCP endpoint is susceptible.

Risk and Exploitability

With a CVSS score of 6.3 the flaw is considered medium severity, and an EPSS score of < 1% indicates a very low probability of exploitation in the wild. The attacker only needs the ability to open a WebSocket connection to the vulnerable service, so the attack vector is likely remote over TCP. Because the exploit requires a single connection to trigger the resource drain, a determined adversary could use this vector to disrupt service availability or to enable a denial‑of‑service attack as part of a broader compromise.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade websocket-driver to version 0.8.1 or later
  • If upgrading is not immediately possible, limit the process memory or run the service behind a reverse proxy that caps header size to prevent excessive allocation
  • Monitor memory usage for anomalous spikes that may indicate an ongoing header overflow attempt and apply vendor patches as they become available

Generated by OpenCVE AI on July 30, 2026 at 23:32 UTC.

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
  • CWE-770

    Allocation of Resources Without Limits or Throttling

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