VDB

CVE-2026-109829

CVE-2026-109829 PUBLISHED CVSS 7.4 HIGH

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

Reported by openjs · Published October 15, 2026

undici is fixed in 8.12.2 and 7.30.1 (npm)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
undicinpm8.12.2, 7.30.1
node-gypWolfi13.1.0-r1
nodejs24-npmAmazon Linux1:11.19.1-1.24.22.1.1.amzn2023.0.1
nodejs24-docsAmazon Linux1:24.22.1-1.amzn2023.0.1
v8-13.6-develAmazon Linux3:13.6.233.17-1.24.22.1.1.amzn2023.0.1
nodejs24-develAmazon Linux1:24.22.1-1.amzn2023.0.1
nodejs24-libsAmazon Linux1:24.22.1-1.amzn2023.0.1
nodejs24-full-i18nAmazon Linux1:24.22.1-1.amzn2023.0.1
nodejs24Amazon Linux1:24.22.1-1.amzn2023.0.1
undiciundici8.12.2, 7.30.1
undicinodejs8.12.2, 7.30.1

Risk scores

CVSS 3.1
7.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

VendorProductVersions
undiciundici7.0.0, 7.30.1, 8.0.0
wolfinode-gyp0
amazon:2023nodejs24-npm0
amazon:2023nodejs24-docs0
amazon:2023v8-13.6-devel0
amazon:2023nodejs24-devel0
amazon:2023nodejs24-libs0
npmundici7.0.0, 8.0.0
amazon:2023nodejs24-full-i18n0
amazon:2023nodejs240
undiciundici8.12.2, 7.0.0, 7.30.1

Timeline

  • Oct 15, 2026 Coalition ESS Score
  • Oct 15, 2026 CVE Published
  • Oct 16, 2026 EPSS Score (3 in total, the first dated here)
  • Oct 27, 2026 CVE Updated
  • Oct 31, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-109829
vulnetix vdb fixes CVE-2026-109829

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-109829/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›