GHSA-33ph-fccm-39pj: websocket-driver: Resource limit bypass via message compression
The websocket-driver library has a vulnerability when used with the permessage-deflate extension, allowing a WebSocket server or client to accept messages larger than the configured maximum size. This occurs because the size check is performed on compressed message frames rather than on the decompressed message size, potentially leading to resource exhaustion. The issue is fixed in version 0.8.1 by validating message length after decompression. No workarounds are known.
AI Analysis
Technical Summary
The websocket-driver library prior to version 0.8.1 improperly enforces maximum message size limits when used with the permessage-deflate extension. The vulnerability arises because the size checks are applied to the compressed frame length headers instead of the decompressed message size, allowing attackers to bypass resource limits by sending compressed messages that decompress to sizes larger than intended. This can cause applications to consume more resources than expected. The issue is tracked as CVE-2026-54464 and has been patched in version 0.8.1 by verifying message length after processing incoming extensions.
Potential Impact
Applications using websocket-driver with the permessage-deflate extension may accept messages exceeding their configured maximum size, leading to potential resource exhaustion or denial of service due to unexpectedly large decompressed messages. This could degrade application performance or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade websocket-driver to version 0.8.1 or later, where the vulnerability is patched by checking message length after decompression. No other workarounds are currently known.
GHSA-33ph-fccm-39pj: websocket-driver: Resource limit bypass via message compression
Description
The websocket-driver library has a vulnerability when used with the permessage-deflate extension, allowing a WebSocket server or client to accept messages larger than the configured maximum size. This occurs because the size check is performed on compressed message frames rather than on the decompressed message size, potentially leading to resource exhaustion. The issue is fixed in version 0.8.1 by validating message length after decompression. No workarounds are known.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The websocket-driver library prior to version 0.8.1 improperly enforces maximum message size limits when used with the permessage-deflate extension. The vulnerability arises because the size checks are applied to the compressed frame length headers instead of the decompressed message size, allowing attackers to bypass resource limits by sending compressed messages that decompress to sizes larger than intended. This can cause applications to consume more resources than expected. The issue is tracked as CVE-2026-54464 and has been patched in version 0.8.1 by verifying message length after processing incoming extensions.
Potential Impact
Applications using websocket-driver with the permessage-deflate extension may accept messages exceeding their configured maximum size, leading to potential resource exhaustion or denial of service due to unexpectedly large decompressed messages. This could degrade application performance or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade websocket-driver to version 0.8.1 or later, where the vulnerability is patched by checking message length after decompression. No other workarounds are currently known.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-33ph-fccm-39pj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-54464"]
- Ecosystems
- ["RubyGems"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a58b41268715ace43d68264
Added to database: 07/16/2026, 10:36:02 UTC
Last enriched: 07/16/2026, 10:54:00 UTC
Last updated: 07/17/2026, 03:40:59 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.