https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-01T22:38:13.669080+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-54465 CVE-2026-54465 — websocket-driver: Memory exhaustion in HTTP header parser 2026-10-01T22:38:13.671215+00:00

Affected: faye websocket-driver-ruby

websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, when websocket-driver is used to implement a WebSocket server on top of a TCP server using WebSocket::Driver.server() or to complement a WebSocket client, a peer can make a single connection consume an unbounded amount of memory by sending an HTTP request or response with a never-ending list of headers. This can lead to the receiving process running out of memory. This issue is fixed in version 0.8.1.

 https://vulnerability.circl.lu/vuln/ghsa-8j3g-f24p-4mpw GHSA-8j3g-f24p-4mpw — websocket-driver: Memory exhaustion in HTTP header parser 2026-10-01T22:38:13.671276+00:00

Affected: RubyGems: websocket-driver

### Impact

If this library is used to implement a WebSocket server on top of a TCP server (rather than an HTTP server or framework) using the `WebSocket::Driver.server()` method, or, if it is used to complement a WebSocket client, then a peer can make a single connection consume an unbounded amount of memory by sending an HTTP request or response with a never-ending list of headers. This can lead to the receiving process running out of memory.

### Patches

The issue has been patched in version 0.8.1, by limiting the total size of HTTP request/response lines and headers accepted by the parser to 32 kB. 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.