p PatchFirst

CVE-2026-54463

CVE-2026-54463 · websocket-driver: Memory exhaustion via abuse of protocol length headers

CVSS 6.9 · Medium · EPSS 0.5% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="ruby-websocket-driver"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

Published
Updated

Stack: system · ruby

Affected products and versions

  • websocket-driver-ruby

    Versions
    • < 0.8.1: Affected

    No fix published

  • ruby-websocket-driver Debian 12

    Versions
    • 0.6.3-3
    • 0.8.0-1
    • 0.8.1-1
    • 0.8.2-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Debian 13

    Versions
    • 0.6.3-3
    • 0.8.0-1
    • 0.8.1-1
    • 0.8.2-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Debian 14

    Versions
    • 0.6.3-3
    • 0.8.0-1
    Affected ranges
    • ECOSYSTEM: < 0.8.1-1

    Update to 0.8.1-1

  • websocket-driver RubyGems

    Versions
    • 0.1.0
    • 0.2.0
    • 0.2.1
    • 0.2.2
    • 0.2.3
    • 0.3.0
    All versions (32)
    • 0.3.1
    • 0.3.2
    • 0.3.3
    • 0.3.4
    • 0.3.5
    • 0.4.0
    • 0.5.0
    • 0.5.1
    • 0.5.2
    • 0.5.3
    • 0.5.4
    • 0.6.0
    • 0.6.1
    • 0.6.2
    • 0.6.3
    • 0.6.4
    • 0.6.5
    • 0.7.0
    • 0.7.1
    • 0.7.2
    • 0.7.3
    • 0.7.4
    • 0.7.5
    • 0.7.6
    • 0.7.7
    • 0.8.0
    Affected ranges
    • ECOSYSTEM: < 0.8.1

    Update to 0.8.1

  • ruby-websocket-driver Ubuntu 16.04 LTS

    Versions
    • 0.6.3-1
    • 0.6.3-1build1
    • 0.6.3-2
    • 0.6.3-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Ubuntu 18.04 LTS

    Versions
    • 0.6.3-2build1
    • 0.6.3-2build2
    • 0.6.3-2build3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Ubuntu 20.04 LTS

    Versions
    • 0.6.3-2build3
    • 0.6.3-2build4
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Ubuntu 22.04 LTS

    Versions
    • 0.6.3-3build1
    • 0.6.3-3build2
    • 0.6.3-3build3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Ubuntu 24.04 LTS

    Versions
    • 0.6.3-3build5
    • 0.6.3-3build6
    • 0.6.3-3build7
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Ubuntu 26.10

    Versions
    • 0.6.3-3ubuntu1
    • 0.8.2-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-websocket-driver Ubuntu 26.04 LTS

    Versions
    • 0.6.3-3ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →