CVE-2026-54490Medium▾ Sunlitwebsocket-driver: Resource limit bypass via message compression
▾ Sunlit zone — Low / medium · no exploitation signal
impact 27.5 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 29.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via GHSA
0.3%
0.3% → 0.4%
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.
The issue has been patched in version 0.7.5, by checking the length of messages after they are processed by incoming extensions. All users should upgrade to this version.
No known workarounds exist.
This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.
websocket-driver < 0.7.5Upgrade to a patched release:
websocket-driver 0.7.5Connected by shared product, vendor, weakness, or advisory.
CVE-2026-54466Criticalwebsocket-driver: Message corruption via abuse of protocol length headers
CVE-2026-54464Mediumwebsocket-driver: Resource limit bypass via message compression
CVE-2026-61666High· 7.5websocket-driver is a WebSocket protocol handler with pluggable I/O
CVE-2026-54463Mediumwebsocket-driver: Memory exhaustion via abuse of protocol length headers
CVE-2026-54465Mediumwebsocket-driver: Memory exhaustion in HTTP header parser
CVE-2025-11362High· 7.5Versions of the package pdfmake from 0.3.0-beta.1 and before 0.3.0-beta.17 are vulnerable to Allocation of Resources Without Limits or Throttling via repeatedly redirect URL in file embedding