Skip to main content
CVE-2026-119790VulnerabilityPublished

Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()

Affects nextSource GCVE Database

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

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

Data as of 16 Nov 2026, 19:52 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 15 Nov 2026.

What to do

Upgrade next to 16.4.5.

Affected software

ProductAffectedFixed in
npmnextAffected
  • >=16.3.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

Upgrade Next.js to version 16.4.5 or later, where this issue is fixed. Alternatively, avoid nesting 'use cache' functions inside unstable_cache(), as this currently throws an error and prevents the vulnerability. No other mitigations are documented.

Description

Next.js versions 16.3.0 through 16.4.4 have a vulnerability where cached data can be disclosed across root route parameters when a 'use cache' function is called both directly during rendering and through unstable_cache(). This occurs due to a race condition during cold process start causing cache entries to be shared improperly across requests with different root params. The issue is fixed in version 16.4.5.

References

Community reviews

Loading reviews…