Skip to main content
CVE-2026-116630VulnerabilityPublished Updated

Nodejs:

Affects nodejsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116630· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium · fixed in 7.30.2 : update nodejs when convenient.

Data as of 18 Nov 2026, 15:20 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.15.9
Patch
Available – fixed in 7.30.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10node-undicipkg:deb/ubuntu/node-undici?arch=source&distro=stonkingOther threatsAffected
  • 7.18.2+dfsg+~cs3.2.0-1build1 – 8.9.0+dfsg+~cs3.2.0-1
5 affected builds
Fixed in–
Ubuntu 26.10nodejspkg:deb/ubuntu/nodejs?arch=source&distro=stonkingOther threatsAffected
  • 22.22.1+dfsg+~cs22.19.15-1ubuntu1 – 24.19.0+dfsg+~cs24.13.3-1ubuntu1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSnode-undicipkg:deb/ubuntu/node-undici?arch=source&distro=resoluteOther threatsAffected
  • 7.3.0+dfsg1+~cs24.12.11-2 – 7.18.2+dfsg+~cs3.2.0-1build1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=resoluteOther threatsAffected
  • 20.19.4+dfsg-1 – 22.22.1+dfsg+~cs22.19.15-1ubuntu1
6 affected builds
Fixed in–
Ubuntu 24.04 LTSnode-undicipkg:deb/ubuntu/node-undici?arch=source&distro=nobleOther threatsAffected
  • =5.22.1+dfsg1+~cs20.10.10.2-1ubuntu1
  • =5.26.3+dfsg1+~cs23.10.12-2
Fixed in–
Ubuntu 24.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=nobleOther threatsAffected
  • 18.13.0+dfsg1-1ubuntu2 – 18.19.1+dfsg-6ubuntu5
5 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…