undici vulnerable to cross-user cache disclosure via same-origin redirect
- 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
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 21st percentile
- 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? →
- 24/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 leak another user's cached private response when the redirect interceptor and a shared response cache are used together and an authenticated request is redirected to a same-origin target. An attacker can reach this remotely, without logging in, and gain access to private response bodies belonging to other users.
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 redirect interceptor and a shared response cache are used together, an authenticated request that is redirected to a same-origin target has the final response stored under the original request's cache key. That key omits the credential and carries no Vary header, so a later anonymous or different user can be served the first user's private response body. This results in cross-user disclosure of cached private responses. The issue is fixed in undici 7.30.2 and 8.12.4, and users should upgrade to one of those versions or later.
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
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 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-120474
Is CVE-2026-120474 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-120474?
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-120474?
Upgrade to a fixed version: 7.30.2, 8.12.4.Source: cve.now feed data