p PatchFirst

PatchFirst · Latest vulnerabilities

ruby-websocket-driver vulnerabilities

Vulnerabilities published for ruby-websocket-driver in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 4

  1. CVE-2026-61666

    High · CVSS 8.9EPSS 0.45%Fix available

    websocket-driver: Denial of service via malformed Host header

    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.

    • Update to 0.8.2-1
    Published Updated
  2. CVE-2026-54465

    Medium · CVSS 6.3EPSS 0.49%Fix available

    websocket-driver: Memory exhaustion in HTTP header parser

    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.

    • Update to 0.8.1-1
    Published Updated
  3. CVE-2026-54463

    Medium · CVSS 6.9EPSS 0.49%Fix available

    websocket-driver: Memory exhaustion via abuse of protocol length headers

    websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.

    • Update to 0.8.1-1
    Published Updated
  4. CVE-2026-54464

    Medium · CVSS 6.3EPSS 0.45%Fix available

    websocket-driver: Resource limit bypass via message compression

    ### 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

    • Update to 0.8.1-1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →