undici vulnerable to Denial of Service via unhandled exception in cache-interceptor response replay
- Exploited
- No known exploitation
- Fix
- Fixed in 7.30.2, 8.12.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.30.2, 8.12.4.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Undici, an HTTP client for Node.js, can be crashed through its cache interceptor when a malicious or compromised HTTP server sends a cacheable response that raises an unhandled exception on replay, terminating the Node.js process. The attack can be launched remotely without logging in or any user action, and it affects availability only.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when the cache interceptor is composed with a downstream handler that throws during response processing (such as the built-in dump interceptor exceeding its maxSize, or the decompress interceptor rejecting more than five Content-Encoding values), a throw raised asynchronously while a cached response is replayed escapes as an uncaught exception or unhandled promise rejection and terminates the Node.js process. A malicious or compromised HTTP server can crash any such client by serving a cacheable response that triggers the throw on replay, including on a 304 revalidation of a stale entry, so the impact is availability only. The issue is fixed in undici 7.30.2 and 8.12.4, and users should upgrade to one of those versions or later. As a workaround, avoid composing the cache interceptor with a response handler that throws during response processing until upgrading.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.30.2, 8.12.4.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- undici undici
From 7.0.0 · fixed in 7.30.2; From 8.0.0 · fixed in 8.12.4
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120222
Is CVE-2026-120222 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-120222?
undici: from 7.0.0 before 7.30.2; from 8.0.0 before 8.12.4.Source: cve.now feed data
How do I fix CVE-2026-120222?
Upgrade to a fixed version: 7.30.2, 8.12.4.Source: cve.now feed data