CVE-2026-109829: undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
undicito a version that resolves this vulnerability.Fixed in 7.30.1 - Upgrade
Upgrade
undicito a version that resolves this vulnerability.Fixed in 8.12.2 - Compensating control
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.
Event History
Frequently Asked Questions
Which deployments are affected?
Applications are affected only if they use an originless Agent, a shared cache store, and compose the redirect interceptor before the cache interceptor. Deployments missing any of these conditions are not described as affected.
What does an attacker need to exploit this issue?
An attacker must control the target of a redirect originating from a trusted URL. They can cause their response to be cached under the trusted URL's original cache key and later served to other callers.
Can this expose data across users?
Yes. A private, non-stored redirect response for a user-specific resource can be stored under the original URL and then served to a later unauthenticated caller, disclosing private data.
Which versions contain the fix?
The issue is fixed in undici 7.30.1 and 8.12.2. Users should upgrade to one of those versions or later.
How can I determine whether my application is exposed?
Review the Agent and interceptor configuration rather than only the installed package version. Exposure requires an originless Agent, a shared cache store, and redirect-then-cache interceptor composition.