Skip to main content
VulnerabilityPublished

CVE-2026-120222: undici · Uncaught Exception

Affects undiciSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.12.4 or 7.30.2 when convenient.

Data as of 6 Nov 2026, 10:20 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.15.9
Patch
Available – fixed in 8.12.4, 7.30.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade undici to 8.12.4 or 7.30.2.

Affected software

ProductAffectedFixed in
undiciundiciAffected
  • >=8.0.0 <8.12.4
Fixed in
  • 8.12.4
undiciundiciAffected
  • >=7.0.0 <7.30.2
Fixed in
  • 7.30.2
npmundicipkg:npm/undiciOther threatsAffected
  • >=7.0.0 <7.30.2
  • >=8.0.0 <8.12.4
Fixed in
  • 7.30.2
  • 8.12.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in undici versions 7.30.2 and 8.12.4. Users should upgrade to these versions or later to remediate the vulnerability. As a temporary workaround before upgrading, avoid composing the cache interceptor with response handlers that may throw exceptions during response processing.

Description

CVE-2026-120222 is a vulnerability in the undici HTTP client for Node.js affecting versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3. When the cache interceptor is used with a downstream handler that throws during response processing, an asynchronous exception can escape as an uncaught exception or unhandled promise rejection, causing the Node.js process to terminate. This can be triggered by a malicious or compromised HTTP server serving a cacheable response that causes the throw on replay, including during 304 revalidation of stale cache entries. The impact is denial of service (availability). The issue is fixed in versions 7.30.2 and 8.12.4, and users are advised to upgrade to these or later versions. As a temporary workaround, avoid composing the cache interceptor with response handlers that throw until patched.

References

Community reviews

Loading reviews…