CVE-2026-54464

websocket-driver: Resource limit bypass via message compression

Published Jul 17, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
### Impact

If this library is used in tandem with the `permessage-deflate` extension, a
WebSocket server or client can be made to accept messages that are larger than
the configured maximum message size. This is because this limit is checked
against the message frames' length headers, which give the size of the
compressed data, not the size after decompression. This can lead to applications
accepting larger messages than expected and exceeding their intended resource
usage.

### Patches

The issue has been patched in version 0.8.1, by checking the length of messages
after they are processed by incoming extensions. All users should upgrade to
this version.

### Workarounds

No known workarounds exist.

### Acknowledgements

This issue was discovered and reported by Pranjali Thakur, DepthFirst Security
Research Team.

Analysis

AI-generated

Technical impact

The library incorrectly verifies the configured maximum message size against the length header of compressed frames, not the size after decompression. As a result, a malicious sender can deliver a compressed payload that uncompresses to a size greater than the allowed limit. This bypass lets the server accept and process oversized messages, potentially exhausting memory or other resources and leading to application instability or denial of service. The weakness is a CWE-770, pathological resource consumption.

Affected Systems

The vulnerability affects the faye websocket-driver-ruby library. Versions prior to 0.8.1 are impacted. Applications that use this library in conjunction with the permessage‑deflate WebSocket extension are at risk.

Risk and Exploitability

The score of 6.3 indicates a moderate severity. EPSS is less than one percent, suggesting a low probability that this flaw will be actively exploited in the wild. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that an attacker must be able to establish a WebSocket connection that negotiates the permessage‑deflate extension and then transmit a carefully crafted compressed frame. If successful, the server would allocate memory for and process the uncompressed message, potentially causing a denial of service. No public workaround is available, so prevention relies on applying the patch.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to websocket-driver-ruby 0.8.1 or a newer version that enforces the size check after decompression, addressing the CWE-770 resource exhaustion weakness.
  • Disable the permessage‑deflate WebSocket extension in server and client configurations when it is not required, to prevent the bypassing of the maximum message size limit inherent to CWE-770.
  • Add application‑level enforcement of payload size limits after decompression to guard against any remaining edge cases and mitigate CWE-770.

Generated by OpenCVE AI on August 1, 2026 at 08:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-33ph-fccm-39pj websocket-driver: Resource limit bypass via message compression
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': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description ### Impact If this library is used in tandem with the `permessage-deflate` extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size. This is because this limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. ### Patches The issue has been patched in version 0.8.1, by checking the length of messages after they are processed by incoming extensions. All users should upgrade to this version. ### Workarounds No known workarounds exist. ### Acknowledgements This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.
Title websocket-driver: Resource limit bypass via message compression
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 21, 2026, 2:13 AM
Reserved
Jun 15, 2026, 3:30 PM
Status
Deferred
Published
Jul 17, 2026, 8:17 PM
Modified
Oct 24, 2026, 8:10 PM