Is CVE-2026-54465 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54465 being exploited in the wild.

How severe is CVE-2026-54465?

Medium severity, with a CVSS score of 4, published 17 July 2026.

Which products and versions are affected?

websocket-driver (RubyGems) < 0.8.1, ECOSYSTEM:introduced=0,fixed=0.8.1.

Is there a fix for CVE-2026-54465?

Yes. websocket-driver (RubyGems): upgrade to 0.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54465 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54465?

Check whether you run websocket-driver (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54465: faye websocket-driver memory exhaustion in HTTP header parser

Q: Is there a fix for CVE-2026-54465?

Yes. websocket-driver (RubyGems): upgrade to 0.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-54465 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-54465?

Check whether you run websocket-driver (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54465 · Severity: medium · CVSS 4 · Published 2026-07-17

A vulnerability in the websocket-driver library can allow an attacker to crash a server or client application by exhausting its available memory. This occurs when the library is used to handle WebSocket connections and receives a specially crafted request with an endless list of headers. An exploit could lead to a denial-of-service, making the affected application or service unavailable to legitimate users.

Technologies: websocket-driver (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2026-54465 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54465 being exploited in the wild.
How severe is CVE-2026-54465?: Medium severity, with a CVSS score of 4, published 17 July 2026.
Which products and versions are affected?: websocket-driver (RubyGems) < 0.8.1, ECOSYSTEM:introduced=0,fixed=0.8.1.
Is there a fix for CVE-2026-54465?: Yes. websocket-driver (RubyGems): upgrade to 0.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54465 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54465?: Check whether you run websocket-driver (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

websocket-driver (RubyGems): upgrade to 0.8.1 or later
```
bundle update websocket-driver
```

Technical details

A resource exhaustion vulnerability (CWE-770) exists in websocket-driver prior to version 0.8.1. When the library is used to implement a WebSocket server via WebSocket::Driver.server() or as a client complement, the HTTP header parser fails to enforce limits on the number or size of incoming headers. A remote attacker can exploit this by sending a continuous stream of HTTP headers, causing the process to allocate memory indefinitely until it crashes or becomes unresponsive. The issue is resolved in version 0.8.1 by implementing a 32 KB limit on the total size of the HTTP request/reponse line and headers.

Affected products

faye websocket-driver-ruby < 0.8.1

Identifiers

CVE-2026-54465
GHSA-8j3g-f24p-4mpw

Timeline

2026-06-04: advisory: GitHub Security Advisory published by maintainer
2026-07-17: disclosed: CVE-2026-54465 published to NVD
2026-07-17: patched: Version 0.8.1 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.