# CVE-2026-120474: undici vulnerable to cross-user cache disclosure via same-origin redirect


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** AZL-113242, DEBIAN-CVE-2026-120474, GHSA-7xg3-fphp-28hg, UBUNTU-CVE-2026-120474

## What is CVE-2026-120474?

CVE-2026-120474 is a medium-severity vulnerability in undici, published on 6 Nov 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-524 (Use of Cache Containing Sensitive Information)

## Which versions are affected by CVE-2026-120474?


## How do I fix CVE-2026-120474?

Upgrade to a fixed version.

## Is CVE-2026-120474 being exploited?

There is no known exploitation of CVE-2026-120474 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120474 and fix it if it is affected.

What it is: CVE-2026-120474 is a medium-severity vulnerability in undici, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120474 in the wild and no public exploit code.

Affected product: undici. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120474/ (Markdown: https://insights.sbomify.com/CVE-2026-120474/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120474
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120474
- OSV: https://osv.dev/vulnerability/CVE-2026-120474

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120474/
Summaries are generated and may contain mistakes; the official description above is the record.
