Skip to main content
← Vulnerabilities

undici vulnerable to cross-user information disclosure via cross-origin redirect revalidation

5.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 7.30.2, 8.12.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.30.2, 8.12.4.

Published
Last modified
23/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

undici, an HTTP client for Node.js, can leak one origin's cached authenticated response to a different caller when a shared cache revalidates it after a cross-origin redirect. An attacker can reach this remotely, without logging in, and read data meant for another user.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, when an Agent composes the redirect and shared cache interceptors, a cached response that is revalidated with a conditional request can be validated by a 304 Not Modified from a different origin. When the origin that stored the response redirects the conditional revalidation request to another origin, the redirect handler strips origin-bound credential headers but not the cache-generated If-None-Match or If-Modified-Since validators, so the redirect destination receives the original origin's validator and undici treats its 304 as successful revalidation of the stored representation. As a result, a shared cache can serve the original origin's stored authenticated response, including one gated by Authorization, to a later unauthenticated caller. The issue is fixed in undici 7.30.2 and 8.12.4, and users should upgrade to one of those versions or later. As a workaround, compose the interceptors as cache then redirect, use per-origin dispatchers and cache stores, or disable shared caching on redirect-capable requests.

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.30.2, 8.12.4.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • undici undici

    From 7.0.0 · fixed in 7.30.2; From 8.0.0 · fixed in 8.12.4

Evidence 2

  1. Advisory
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-116630

Is CVE-2026-116630 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-116630?

undici: from 7.0.0 before 7.30.2; from 8.0.0 before 8.12.4.Source: cve.now feed data

How do I fix CVE-2026-116630?

Upgrade to a fixed version: 7.30.2, 8.12.4.Source: cve.now feed data