Vulnerabilities in pkg:npm/websocket-driver

PACKAGE
Advisory Identifier: GHSA-mp7j-qc5w-4988
Share
Advisory Summary

CVE-2026-54490 is a MODERATE remote code execution vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting websocket-driver libraries in the npm ecosystem. The issue involves resource limit bypass via message compression. Remediation is available by upgrading affected packages to version 0.7.5.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/websocket-driver

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/websocket-driver. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-mp7j-qc5w-4988 CVE-2026-54490 MODERATE websocket-driver: Resource limit bypass via message compression
GHSA-xv26-6w52-cph6 CVE-2026-54466 CRITICAL websocket-driver: Message corruption via abuse of protocol length headers

CVE-2026-54490 at a Glance

CVE Identifier CVE-2026-54490
GHSA Identifier GHSA-mp7j-qc5w-4988
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product websocket-driver
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-54490

To remediate this vulnerability, upgrade all affected websocket-driver dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

websocket-driver fixed: 0.7.5 
npm install websocket-driver@0.7.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls websocket-driver

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-54490, inspect your project dependencies using npm:

npm ls websocket-driver

Analyze the terminal output to locate any version of websocket-driver in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.7.5), your application is affected.

Note: The npm ls websocket-driver command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In websocket-driver, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-54490 Affected websocket-driver Versions

1 component(s)
Fixed Versions:
0.7.5
Product / Package Ecosystem Affected Versions Fixed Version
websocket-driver
npm/websocket-driver
npm
< 0.7.5
0.7.5

References

GitHub Advisory / Wiki ADVISORY
https://github.com/faye/websocket-driver-node/security/advisories/GHSA-mp7j-qc5w-4988
websocket-driver Source Repository REPOSITORY
https://github.com/faye/websocket-driver-node
websocket-driver Release RELEASE
https://github.com/faye/websocket-driver-node/releases/tag/0.7.5

Frequently Asked Questions

What is CVE-2026-54490?
CVE-2026-54490 is a security vulnerability in websocket-driver involving Resource limit bypass via message compression under CWE-770: Allocation of Resources Without Limits or Throttling.
Which websocket-driver versions are affected?
Affected versions include releases prior to 0.7.5 across affected packages: websocket-driver.
What version fixes CVE-2026-54490?
Upgrading to 0.7.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is websocket-driver affected?
Yes, websocket-driver is affected in releases prior to 0.7.5. Upgrade your dependency to 0.7.5 or later.
What CWE is associated with CVE-2026-54490?
CVE-2026-54490 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check npm dependencies for CVE-2026-54490?
Run the dependency tree command: 'npm ls websocket-driver'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mp7j-qc5w-4988",
  "modified" : "2026-07-15T22:08:17Z",
  "published" : "2026-07-15T22:08:17Z",
  "aliases" : [ "CVE-2026-54490" ],
  "summary" : "websocket-driver: Resource limit bypass via message compression",
  "details" : "### Impact\n\nIf 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.\n\n### Patches\n\nThe 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.\n\n### Workarounds\n\nNo known workarounds exist.\n\n### Acknowledgements\n\nThis issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "websocket-driver"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.7.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/faye/websocket-driver-node/security/advisories/GHSA-mp7j-qc5w-4988"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/faye/websocket-driver-node"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/faye/websocket-driver-node/releases/tag/0.7.5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-15T22:08:17Z",
    "nvd_published_at" : null
  }
}