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

Summary

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.

Timeline

1. Oct 15, 2026, 6:28 PM UTCCVE published
2. Oct 16, 2026, 8:03 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Oct 16, 2026, 8:04 PM UTCRecord last updated

Affected versions

• undici undici

  From 7.0.0 · fixed in 7.30.1; From 8.0.0 · fixed in 8.12.2

• undicinpm

  From 7.0.0 · fixed in 7.30.1

• undicinpm

  From 8.0.0 · fixed in 8.12.2

References 2