undici vulnerable to cross-origin credential disclosure via array-of-tuples headers bypassing redirect stripping
- 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 disclose the caller's credentials, such as Authorization and Cookie headers, to an unrelated site after a cross-origin redirect. An attacker can reach this remotely, without logging in or any user action, when request headers are passed as an array of name and value tuples and a cache or deduplicate interceptor is composed outside the redirect interceptor.
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, the redirect interceptor strips sensitive headers such as Authorization, Cookie, Proxy-Authorization, and Host when a request is redirected to a different origin, but when request headers are supplied as an array of name and value tuples (a valid documented input, for example from Object.entries), the redirect handler misreads them as a flat list so the header names never match and the sensitive headers are not removed. If a header-normalizing interceptor such as cache or deduplicate is composed outside the redirect interceptor, it then serializes the retained headers onto the cross-origin request, disclosing the caller's origin-bound credentials to the unrelated redirect destination. This is a representation-dependent bypass of the cross-origin header stripping added in CVE-2024-30260. 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, supply request headers as a plain object or a flat name and value array rather than an array of tuples, or compose the redirect interceptor outside the normalizing interceptor.
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-120415
Is CVE-2026-120415 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-120415?
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-120415?
Upgrade to a fixed version: 7.30.2, 8.12.4.Source: cve.now feed data