Quick answers
- Is CVE-2026-109855 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109855 being exploited in the wild.
- How severe is CVE-2026-109855?
- High severity, with a CVSS score of 7.5, published 15 October 2026.
- Which products and versions are affected?
- Node.js Undici 8.11.0, 8.11.1; undici (npm) >= 8.11.0, < 8.11.2, SEMVER:introduced=8.11.0,fixed=8.11.2.
- Is there a fix for CVE-2026-109855?
- Yes. undici (npm): upgrade to 8.11.2 or later. Until then: Set allowH2 to false to disable HTTP/2 for WebSocket connections, or avoid opening WebSocket connections to untrusted servers until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109855 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-109855?
- Check whether you run Node.js Undici, Nodejs Undici or undici (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- undici (npm): upgrade to 8.11.2 or later
npm install undici@8.11.2
Set allowH2 to false to disable HTTP/2 for WebSocket connections, or avoid opening WebSocket connections to untrusted servers until upgrading.
Technical details
The vulnerability is an unhandled exception in the WebSocket client's HTTP/2 handshake logic: when a WebSocket upgrade fails validation, the abort is marked as a no-op because the request is already completed, leaving the underlying ClientHttp2Stream open without an error listener. When the malicious server closes the connection, the orphaned stream emits an unhandled error that crashes the process. The attack requires network access and an unauthenticated connection to a WebSocket endpoint.
Affected products
- Node.js undici 8.11.0, 8.11.1
Identifiers
- CVE-2026-109855
- GHSA-qq8j-7v2v-3rwp
Timeline
- 2026-10-15: disclosed
- 2026-10-15: patched