How severe is GHSA-ghhp-3qvg-889p?

No CVSS score has been assigned to GHSA-ghhp-3qvg-889p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ghhp-3qvg-889p?

GHSA-ghhp-3qvg-889p affects the following packages: websocket-driver (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-ghhp-3qvg-889p?

Update websocket-driver to 0.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghhp-3qvg-889p is resolved across your whole dependency graph.

How do I detect GHSA-ghhp-3qvg-889p in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for websocket-driver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-ghhp-3qvg-889p if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-ghhp-3qvg-889p actively exploited in the wild?

No public exploit code has been indexed for GHSA-ghhp-3qvg-889p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-ghhp-3qvg-889p?

GHSA-ghhp-3qvg-889p has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-ghhp-3qvg-889p?

GHSA-ghhp-3qvg-889p is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-ghhp-3qvg-889p published, and has it been updated?

GHSA-ghhp-3qvg-889p was published on July 15, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

websocket-driver: Memory exhaustion via abuse of protocol length headersGHSA-ghhp-3qvg-889p

Fix: faye/websocket-driver-ruby@d0141f0

GHSA-ghhp-3qvg-889p is a CWE-770 vulnerability in websocket-driver. A fix is available for websocket-driver — see the affected versions and patch details below.

Also known asCVE-2026-54463

Published

Jul 15, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

💎websocket-driver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory.

Patches

The issue has been patched in version 0.8.1. 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`websocket-driver`	all versions	0.8.1`bundle update websocket-driver --conservative`

Affected Products

1 product · 1 configurations

Application

websocket-driverfaye

< 0.8.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for websocket-driver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update websocket-driver to 0.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghhp-3qvg-889p is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. ### Patches The issue has been patched in version 0.8

O3 Security · Impact-Aware SCA

Is GHSA-ghhp-3qvg-889p in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works