NPM · JULY 2026 · EARLY WARNING

websocket-driver npm Package Under Investigation: Resource Limit Bypass

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-33PH-FCCM-39PJSeverity: HIGH

The websocket-driver npm package, when used with the permessage-deflate extension, is reportedly vulnerable to a resource limit bypass. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage.

What happened

The websocket-driver npm package, when used with the permessage-deflate extension, appears to accept messages larger than the configured maximum size. This can result in applications accepting larger messages than expected, potentially leading to exceeding their intended resource usage. The vulnerability is tracked under GHSA-33PH-FCCM-39PJ. To mitigate this issue, it is recommended to upgrade to websocket-driver@0.8.1. Affected components include websocket-driver (npm) versions prior to 0.8.1. Further details and confirmation should be obtained from the primary sources listed.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If websocket-driver is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats