undici WebSocket client vulnerable to Denial of Service via failed HTTP/2 handshake
Published 27 Oct 2026 · Updated 27 Oct 2026
Affected package
- Affected
- >=8.11.0 <8.11.2
- Fixed in
- 8.11.2
npm install undici@8.11.2Details
Impact
undici's experimental WebSocket client (enabled by default via allowH2: true) crashes the Node.js process when it connects to a malicious server over HTTP/2. If the server answers the WebSocket upgrade with a response that fails handshake validation, undici aborts the request, but the abort is a no-op because the request is already marked completed, so the underlying ClientHttp2Stream is left open with no error listener. When the server then destroys the connection, the orphaned stream emits an unhandled error and the process exits. A remote, unauthenticated server can therefore deny service to any client that opens a WebSocket to it over HTTP/2. undici 8.11.0 and 8.11.1 are affected; the regression was introduced in 8.11.0.
Patches
Upgrade to 8.11.2.
Workarounds
Set allowH2: false to disable HTTP/2 for WebSocket connections, or avoid opening WebSocket connections to untrusted servers, until upgrading.
Is GHSA-qq8j-7v2v-3rwp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected undici, and gives you the command that fixes it.
References
- Linkgithub.com/nodejs/undici/security/advisories/GHSA-qq8j-7v2v-3rwp
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-109855
- Linkgithub.com/nodejs/undici/pull/5873
- Linkgithub.com/nodejs/undici/commit/dd28c5c55f4a25f7c441fd4365b1191f96c3b8bf
- Linkcna.openjsf.org/security-advisories.html
- Packagegithub.com/nodejs/undici
- Linkgithub.com/nodejs/undici/releases/tag/v8.11.2
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.