Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
Affects nextSource GCVE Database
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
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.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:NExploitation evidence
Disclosed: evidence found.
CVE published 16 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 15 Nov 2026.
What to do
Upgrade next to 16.4.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnext | 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
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
- github.com/vercel/next.js/security/advisories/GHSA-mfr8-8qww-v76h (opens in a new tab)
- github.com/vercel/next.js/commit/d605874e5a4b8b6b7dca1b6e07bcabb44d0e2e5b (opens in a new tab)
- github.com/vercel/next.js (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v16.4.5 (opens in a new tab)
- nextjs.org/blog/november-2026-security-release (opens in a new tab)