CVE-2026-109829
undici is an HTTP client library for Node.js
- Risk score
- 70/100
- CVSS
- 9.1 v3.1
- Exploit chance (30 days)
- 0.1%
- Published
- 15 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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, …
- Affected
- Undici
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Story map
At a glance
Undici: Amber, patch this week. undici is an HTTP client library for Node.js. In versions 4.0.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its Agent dispatcher passes its constructor options through a JSON-based deep clone before forwarding them to each per-origin pool, and because JSON cannot represent functions, a caller-suppl…
The flaws
- CVE-2026-109829: Undici is an HTTP client library for Node.js (CVSS 9.1 · EPSS 0%)
- CVE-2026-109383: Undici is an HTTP client library for Node.js (CVSS 9.1 · EPSS 0%)
- CVE-2026-109932: Undici is an HTTP client library for Node.js (CVSS 7.5 · EPSS 0%)
- CVE-2026-109855: Undici is an HTTP client library for Node.js (CVSS 7.5 · EPSS 0%)
The fix
Upgrade Undici: 8.11.2 or later on your release line
Who is exposed: Undici
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-346 (CWE-346). 54 other warnings in 30 days
- Same product: Earlier Undici warnings. 5 in the last 90 days
Why it is Amber
- CVSS 9.1 critical
- Remotely exploitable without logging in
- On your watchlist: node.js
References
Original 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.
Last activity 15 Oct 2026. Patch Forecast updates every hour.