---
id: "CVE-2026-109829"
kind: "vulnerability"
aliases: ["CVE-2026-109829", "GHSA-4w7w-5xrc-9h26"]
title: "undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects"
severity: "critical"
cvss: 9.1
epss: 0.00149
exploited: false
status: "open"
category: "package"
products: [{"name": "undici", "fixed": ["7.30.1"], "affected": ">= 7.0.0, < 7.30.1", "ecosystem": "npm"}, {"name": "undici", "fixed": ["8.12.2"], "affected": ">= 8.0.0, < 8.12.2", "ecosystem": "npm"}, {"name": "nodejs undici", "fixed": ["7.30.1"], "affected": ">= 7.0.0, < 7.30.1", "ecosystem": "vendor"}, {"name": "nodejs undici", "fixed": ["8.12.2"], "affected": ">= 8.0.0, < 8.12.2", "ecosystem": "vendor"}]
ecosystems: ["npm", "vendor"]
tags: ["cwe-346", "cwe-524", "http-clients", "node.js", "npm", "package", "undici"]
not_affected_if: ["default-config", "no-shared-cache", "origin-bound-dispatchers", "reverse-composition"]
published_at: "2026-10-15T19:17:21+00:00"
first_seen_at: "2026-10-27T19:04:55+00:00"
updated_at: "2026-10-27T19:33:18+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-4w7w-5xrc-9h26", "first_seen_at": "2026-10-27T19:04:55+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109829", "first_seen_at": "2026-10-27T19:33:18+00:00"}]
---

# undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects

When an originless undici Agent composes redirect() before cache() with a shared cache store, a response from a cross-origin redirect target is cached under the original URL. An attacker who controls a redirect target can poison that trusted URL for other callers, and a private no-store redirect response can be served to unauthenticated users.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:undici affected >= 7.0.0, < 7.30.1 fixed 7.30.1
- npm:undici affected >= 8.0.0, < 8.12.2 fixed 8.12.2
- vendor:nodejs undici affected >= 7.0.0, < 7.30.1 fixed 7.30.1
- vendor:nodejs undici affected >= 8.0.0, < 8.12.2 fixed 8.12.2

## How to check

- Run `npm ls undici` to find the installed undici version and whether it is 7.x below 7.30.1 or 8.x below 8.12.2.
- Search code for `compose(redirect(), cache())` together with `new Agent(` and `type: 'shared'` on a MemoryCacheStore or SqliteCacheStore.

## Fix

- Upgrade undici to `7.30.1` (7.x line) or `8.12.2` (8.x line).
- Alternatively, reverse the order to `compose(cache(), redirect())`, use per-origin dispatchers and cache stores, or disable shared caching on redirect-capable requests.

## Timeline

- 2026-10-27T19:04:55+00:00 ghsa https://github.com/advisories/GHSA-4w7w-5xrc-9h26
- 2026-10-27T19:33:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109829

## From the sources

### Impact

When an originless `Agent` composes the redirect and cache interceptors as `compose(redirect(), cache())` with a shared cache (`type: 'shared'`), the cache builds its key from the original request URL before the redirect handler changes the origin. The response produced after a redirect is then stored under the original key, even when the redirect crossed to a different origin.

An attacker who controls the target of a redirect from a trusted URL can have their response cached under that trusted URL. A later caller requesting the trusted URL receives the attacker's body from the shared cache without either origin being contacted, allowing persistent cache poisoning. The same key confusion also discloses private data: when an authenticated request returns a `private, no-store` redirect to a user-specific resource, the final response is stored under the original URL and can be served to a later unauthenticated caller.

The cache interceptor was introduced in undici 7.0.0, and all 7.x and 8.x releases before the patched versions are affected. Applications are affected only when an originless `Agent`, a shared `MemoryCacheStore` or `SqliteCacheStore`, and the composition `compose(redirect(), cache())` are all used. Origin-bound `Client` and `Pool` dispatchers, and the reverse composition `compose(cache(), redirect())`, are not affected.

### Patches

Upgrade to `7.30.1` or `8.12.2`. Before storing a response, undici now verifies that the origin that produced it still matches the cache key, and preserves each redirect hop's cache-control policy, so cross-origin redirect responses and responses behind a `no-store` or `private` hop are no longer cached under the original key.

### Workarounds

Compose the interceptors as `compose(cache(), redirect())`, use per-origin dispatchers and cache stores, or disable shared caching on redirect-capable requests.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_