Skip to main content
CVE-2026-119351VulnerabilityPublished

Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata

Affects nextSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119351· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 16.4.5 when convenient.

Data as of 17 Nov 2026, 16:51 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.3
Patch
Available – fixed in 16.4.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 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 16 Nov 2026.

What to do

Upgrade next to 16.4.5.

Affected software

ProductAffectedFixed in
npmnextAffected
  • >=16.2.0 <16.4.5
Fixed in
  • 16.4.5

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 Next.js version 16.4.5. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A cache leak vulnerability exists in Next.js versions 16.2.0 through 16.4.4 involving nested 'use cache' functions when Cache Components are enabled. An outer 'use cache' function can incorrectly key its cache entry if the inner function reads root parameters and returns data containing pending promises. This causes the outer cache entry to omit root param dependencies, leading to cache entries being reused across different root param values. The leaked content is not attacker-controlled but can cause responses for one root param to serve content intended for another. This issue is fixed in version 16.4.5.

References

Community reviews

Loading reviews…