websocket-driver: Resource limit bypass via message compression (CVE-2026-54490) | HOL Guard CVE

Medium · CVSS 6.3CVE-2026-54490GHSA-MP7J-QC5W-4988

websocket-driver: Resource limit bypass via message compression

Answer in brief

CVE-2026-54490 records a Medium severity (CVSS 6.3) vulnerability in websocket-driver: Resource limit bypass via message compression. The current sources do not mark it as known exploited. The current feed maps websocket-driver (npm), websocket-driver (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 15, 2026Updated Sep 10, 2026Source checked Sep 16, 2026First seen by HOL Jul 15, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.3
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps websocket-driver (npm), websocket-driver (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
websocket-drivernpm	<0.7.5	0.7.5
websocket-drivernpm	>=0 <0.7.5	0.7.5

Recommended response

Check inventory. Check lockfiles and deployed manifests for websocket-driver, websocket-driver.
Review the reported fix. Update websocket-driver to 0.7.5; websocket-driver to 0.7.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 15, 2026
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Jul 15, 2026

Sources and claim methodology

Upstream source description

### 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.7.5, by checking the length of messages after they are processed by incoming extensions. 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.

Quoted source text, attributed separately from HOL analysis.