GEM · JULY 2026 · EARLY WARNING

websocket-driver Gem Vulnerability: Memory Exhaustion via Protocol Length Headers

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-GHHP-3QVG-889PSeverity: HIGH

An early warning has been issued regarding a vulnerability in the websocket-driver gem, versions prior to 0.8.1, which may lead to memory exhaustion through the abuse of protocol length headers.

What happened

The websocket-driver gem, versions prior to 0.8.1, is reportedly vulnerable to memory exhaustion due to an issue with the handling of protocol length headers. An attacker can exploit this by sending an indefinite sequence of bytes with values 0x80 or above, causing the affected system to parse these bytes into an ever-growing integer, resulting in unbounded memory consumption. This can potentially lead to a denial of service condition. It is recommended to upgrade to websocket-driver version 0.8.1 or later to mitigate this risk. The vulnerability is under investigation, and for more detailed information, the primary sources should be consulted.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If websocket-driver is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats