Patch Forecast
Amber warning
Patch this week.

CVE-2026-19534 · GHSA-rfgv-xxqx-mfg5

undici vulnerable to Denial of Service via unrequested WebSocket subprotocol

Risk score
62/100
CVSS
7.5 v3.1
Exploit chance (30 days)
0.4%
Published
29 Sep 2026

Open in the live forecast Today's forecast

What to know

What it is
The undici WebSocket client throws an uncaught TypeError during the opening handshake when a server's 101 response includes a Sec-WebSocket-Protocol header that the client never requested. The throw occurs in a queueMicrotask callback with no surrounding try/catch, so it propagates as an uncaught exception and termina…
Affected
undici (npm) >= 6.7.0, < 6.28.1; undici (npm) >= 7.0.0, < 7.29.1; undici (npm) >= 8.0.0, < 8.10.2
Fix
Upgrade undici to 6.28.1 or 7.29.1 or 8.10.2 (whichever matches your release line) or later.
Exploitation
No known exploitation

Story map

Story map: undiciTHE FLAWSTHE FIXCVE-2026-19534Undici vulnerable to Denial ofService via unrequestedWebSocket subprotocolCVSS 7.5 · EPSS 0%CVE-2026-84961Undici vulnerable to TLScertificate validation bypassvia dropped connect options in…CVSS 7.4 · EPSS 0%CVE-2026-85152Undici vulnerable tocross-origin cache poisoning viamissing origin isolation in…CVSS 7.4 · EPSS 0%CVE-2026-18149Undici vulnerable to Denial ofService via orphanedRetryHandler response bodyCVSS 5.9 · EPSS 0%FixUpgrade undici to 6.28.1 or7.29.1 or 8.10.2 (whichevermatches your release line) orlater.Who is exposedundici (npm) >= 6.7.0, < 6.28.1;undici (npm) >= 7.0.0, < 7.29.1;undici (npm) >= 8.0.0, < 8.10.2AMBER · PATCH THIS WEEKundiciThe undici WebSocket clientthrows an uncaught TypeErrorduring the opening handshakewhen a server's 101 responseincludes aSec-WebSocket-Protocol headerthat the client never…Where it standsNo known exploitationCONNECTS TOSame weaknessCWE-248 (CWE-248)62 other warnings in 30 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

undici: Amber, patch this week. The undici WebSocket client throws an uncaught TypeError during the opening handshake when a server's 101 response includes a Sec-WebSocket-Protocol header that the client never requested. The throw occurs in a queueMicrotask callback with no surrounding try/catch, so it propagates as an uncaught exception and termina…

The flaws

  • CVE-2026-19534: Undici vulnerable to Denial of Service via unrequested WebSocket subprotocol (CVSS 7.5 · EPSS 0%)
  • CVE-2026-84961: Undici vulnerable to TLS certificate validation bypass via dropped connect options in BalancedPool (CVSS 7.4 · EPSS 0%)
  • CVE-2026-85152: Undici vulnerable to cross-origin cache poisoning via missing origin isolation in interceptors (CVSS 7.4 · EPSS 0%)
  • CVE-2026-18149: Undici vulnerable to Denial of Service via orphaned RetryHandler response body (CVSS 5.9 · EPSS 0%)

The fix

Fix: Upgrade undici to 6.28.1 or 7.29.1 or 8.10.2 (whichever matches your release line) or later.

Who is exposed: undici (npm) >= 6.7.0, < 6.28.1; undici (npm) >= 7.0.0, < 7.29.1; undici (npm) >= 8.0.0, < 8.10.2

Where it stands

  • No known exploitation

Connects to

Why it is Amber

  • CVSS 7.5 high
  • Remotely exploitable without logging in
  • On your watchlist: npm

Affected packages

PackageEcosystemVulnerableFixed in
undicinpm>= 6.7.0, < 6.28.16.28.1
undicinpm>= 7.0.0, < 7.29.17.29.1
undicinpm>= 8.0.0, < 8.10.28.10.2

References

Original description

### Impact The undici WebSocket client throws an uncaught `TypeError` during the opening handshake when a server's `101` response includes a `Sec-WebSocket-Protocol` header that the client never requested. The throw occurs in a `queueMicrotask` callback with no surrounding `try`/`catch`, so it propagates as an uncaught exception and terminates the Node.js process. This is a remote, unauthenticated denial of service against any application that opens a WebSocket to an attacker controlled or compromised server, or over a plaintext `ws://` connection subject to a machine-in-the-middle. It affects the default `new WebSocket(url)` usage, where no subprotocol is requested. Per RFC 6455 section 4.1, an unrequested subprotocol must fail the connection, not crash it. All releases starting at undici 6.7.0 are affected. ### Patches Upgrade to undici 6.28.1, 7.29.1, or 8.10.2. ### Workarounds No workaround is available. The fix must be applied through an upgrade.

Last activity 29 Sep 2026. Patch Forecast updates every hour.