websocket-driver: Resource limit bypass via message compression
GHSA-33ph-fccm-39pj · CVE-2026-54464
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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.
References
- WEB https://github.com/faye/websocket-driver-ruby/security/advisories/GHSA-33ph-fccm-39pj
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-54464
- WEB https://github.com/faye/websocket-driver-ruby/commit/fa8641724f10bf3273585f1dcf9041f540bbd036
- PACKAGE https://github.com/faye/websocket-driver-ruby
- WEB https://github.com/faye/websocket-driver-ruby/releases/tag/0.8.1
- WEB https://github.com/rubysec/ruby-advisory-db/blob/master/gems/websocket-driver/CVE-2026-54464.yml
- WEB https://www.cve.org/CVERecord/SearchResults?query=CVE-2026-54464
Ready to move
Start Securing
Free, no credit card | First findings in minutes