CVE-2026-116630: undici · Origin Validation Error
Affects undiciSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.12.4 or 7.30.2 when convenient.
Data as of 6 Nov 2026, 10:48 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 8.12.4, 7.30.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade undici to 8.12.4 or 7.30.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| undiciundici | Affected
| Fixed in
|
| undiciundici | Affected
| Fixed in
|
npmundicipkg:npm/undiciOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in undici versions 7.30.2 and 8.12.4. Users should upgrade to these versions or later to remediate the vulnerability. As a workaround, users can compose interceptors in the order of cache then redirect, use per-origin dispatchers and cache stores, or disable shared caching on requests that can be redirected. These mitigations reduce the risk until the official fix is applied.
Description
A vulnerability in undici HTTP client for Node.js versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3 allows a shared cache to serve an authenticated response to an unauthenticated caller due to improper origin validation during redirect and cache revalidation. This occurs when a cached response is revalidated with a 304 Not Modified status from a different origin, causing undici to incorrectly treat the response as valid. The issue is fixed in versions 7.30.2 and 8.12.4. Users should upgrade to these versions or later or apply recommended workarounds to mitigate the risk.