MediumGHSA-33ph-fccm-39pjCVE-2026-54464

websocket-driver: Resource limit bypass via message compression

Published 15 Jul 2026 · Updated 10 Sept 2026

Is your project on an affected websocket-driver?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.8.1
Fixed in
0.8.1
Update to the fixed version for your release line, for example:bundle update --conservative websocket-driver # Gemfile: '>= 0.8.1'

Details

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.

Is GHSA-33ph-fccm-39pj in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected websocket-driver, and gives you the command that fixes it.

More advisories for websocket-driver

  • HighCVE-2026-61666websocket-driver-ruby: Denial of service via malformed Host header · 21 Jul 2026
  • MediumCVE-2026-54465websocket-driver: Memory exhaustion in HTTP header parser · 15 Jul 2026
  • MediumCVE-2026-54463websocket-driver: Memory exhaustion via abuse of protocol length headers · 15 Jul 2026
websocket-driver security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.