{"id":"CVE-2026-54490","aliases":["GHSA-mp7j-qc5w-4988"],"title":"websocket-driver: Resource limit bypass via message compression","summary":"websocket-driver: Resource limit bypass via message compression","severity":"medium","cwe":["CWE-770"],"vendor":"websocket-driver","product":"websocket-driver","ecosystem":"npm","affected":["websocket-driver < 0.7.5"],"patched":["websocket-driver 0.7.5"],"published":"2026-07-15","updated":"2026-07-15","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-mp7j-qc5w-4988","references":[{"url":"https://github.com/faye/websocket-driver-node/security/advisories/GHSA-mp7j-qc5w-4988"},{"url":"https://github.com/faye/websocket-driver-node/releases/tag/0.7.5"},{"url":"https://github.com/advisories/GHSA-mp7j-qc5w-4988"}],"tags":["ghsa","npm"],"ingestedAt":"2026-07-15T22:46:58.771Z","epss":0.00445,"epssPercentile":0.35948,"slug":"CVE-2026-54490","body":"## Overview\n\n### Impact\n\nIf 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.\n\n### Patches\n\nThe 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.\n\n### Workarounds\n\nNo known workarounds exist.\n\n### Acknowledgements\n\nThis issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.\n\n## Affected packages\n\n- `websocket-driver < 0.7.5`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `websocket-driver 0.7.5`","depth":"sunlit","depthScore":28,"depthScoreParts":{"impact":27.5,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}