CVE-2026-54463

websocket-driver: Memory exhaustion via abuse of protocol length headers

Published Jul 17, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.

Analysis

AI-generated

Technical impact

The driver contains a flaw in its handling of WebSocket protocol length headers. The length header can encode an arbitrarily large integer using high‑bit bytes, and the parser will expand that into an ever‑growing Ruby integer. This flaw is a memory allocation issue (CWE‑770). An attacker can send a crafted WebSocket message that forces this integer to grow without bound, exhausting the process’s memory and causing it to crash or become unresponsive, leading to a denial of service rather than code execution.

Affected Systems

Faye’s websocket‑driver‑ruby is affected in all releases before version 0.8.1. Any installed instance of the driver that has not been updated to 0.8.1 or later is vulnerable.

Risk and Exploitability

The CVSS score of 6.9 indicates moderate to high severity, and the EPSS score of less than 1% suggests exploitation opportunities are currently low. The vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is remote, via a client that initiates a WebSocket connection to a server or client using the vulnerable driver. An adversary can trigger the exhaustion by repeatedly sending oversized length‑header fields, leading to memory exhaustion and denial of service at the victim host.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade websocket‑driver‑ruby to version 0.8.1 or later.
  • If a version upgrade is not feasible, restrict or disable WebSocket traffic that relies on the vulnerable driver, or use a proxy that validates and limits header lengths.
  • Implement operating‑system or container resource limits to cap the memory usage of the process that uses websocket‑driver, thereby protecting the system from complete exhaustion.

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-ghhp-3qvg-889p websocket-driver: Memory exhaustion via abuse of protocol length headers
History
Type Values Removed Values Added
Metrics ssvc

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

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
Description websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.
Title websocket-driver: Memory exhaustion via abuse of protocol length headers
Weaknesses CWE-770
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/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, 4:58 PM
Reserved
Jun 15, 2026, 3:30 PM
Status
Analyzed
Published
Jul 17, 2026, 8:17 PM
Modified
Oct 24, 2026, 8:10 PM