https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-29T17:58:56.969334+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-61666 CVE-2026-61666 — websocket-driver: Denial of service via malformed Host header 2026-09-29T17:58:57.009821+00:00

Affected: faye websocket-driver-ruby

websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.2, WebSocket::Driver.server() passes a malformed Host header to URI.parse in lib/websocket/http/request.rb without catching URI::InvalidURIError, allowing a remote client to crash a TCP-backed WebSocket server when the application does not catch the error from parse(). This issue is fixed in version 0.8.2.

 https://vulnerability.circl.lu/vuln/ghsa-2x63-gw47-w4mm GHSA-2x63-gw47-w4mm — websocket-driver-ruby: Denial of service via malformed Host header 2026-09-29T17:58:57.009933+00:00

Affected: RubyGems: websocket-driver

### Impact

If this library is used to implement a WebSocket server on top of a TCP server, by using the `WebSocket::Driver.server()` method, then a client can cause the server to crash by sending a `Host` header that is not a valid `host[:port]` string. When this happens, a `URI::InvalidURIError` exception is raised which is not caught, and this can cause the server process to crash if the application does not catch the error from the `parse()` method itself.

### Patches

The issue has been patched in version 0.8.2 by making the request parser catch `URI::InvalidURIError` and enter an error state if the `Host` header is malformed. This means the request is considered invalid and should not establish a WebSocket connection.

### Workarounds

No known workarounds exist.

### Acknowledgements

This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.