CVE-2026-109829
7.4HighPublished 15 Oct 2026 · NVD status: Undergoing Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on confidentiality, integrity
- Weakness
- CWE-346, CWE-524
Impact
Remote attackers controlling a redirect target can poison the cache for trusted URLs or expose sensitive redirect responses to unauthorized users. They need the application to follow a redirect to a malicious or private destination using a shared cache.
Root cause
The cache interceptor derives cache keys from the initial request URL before cross-origin redirects occur, caching redirect responses under the wrong origin.
Affected systems
undici 7.0.0 through 7.30.0 and 8.0.0 through 8.12.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Fix & remediation
Upgrade to undici 7.30.1 or 8.12.2. If patching immediately is not possible, reorder interceptors so cache runs before redirect, switch to per-origin dispatchers with dedicated cache stores, or disable shared caching for requests that handle redirects.
$ npm install undici@latestAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
undici is an HTTP client library for Node.js. In versions 7.0.0 through 7.30.0 and 8.0.0 through 8.12.1, when an originless Agent composes the redirect and cache interceptors in that order with a shared cache store, the cache builds its key from the original request URL before the redirect handler changes the origin, so a response produced after a cross-origin redirect is stored under the original key. An attacker who controls the target of a redirect from a trusted URL can have their response cached under that trusted URL and served to later callers, allowing persistent cache poisoning, and the same key confusion lets a private, non-stored redirect response to a user-specific resource be stored under the original URL and served to a later unauthenticated caller, disclosing private data. Applications are affected only when an originless Agent, a shared cache store, and the redirect-then-cache composition are all used. The issue is fixed in undici 7.30.1 and 8.12.2, which verify the producing origin still matches the cache key and preserve each redirect hop's cache-control policy before storing, and users should upgrade to one of those versions or later. As a workaround, compose the cache interceptor before the redirect interceptor, use per-origin dispatchers and cache stores, or disable shared caching on redirect-capable requests.