CVE-2026-119351
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
Impact
Next.js is a React framework for building full-stack web applications. From 16.2.0 until 16.4.5, Next.js applications with Cache Components enabled can reuse an outer 'use cache' entry across root param values when a nested 'use cache' call reads a root param through next/root-params and returns a value containing pending promises. React Flight can deliver the ready portion to the outer function before the inner cache finishes publishing its root-param dependencies. The outer entry can then complete and be persisted under a key that omits the root param, causing the first written value to be served for other root param values and allowing the outer entry to ignore nested cache tag invalidation and lifetimes. The leaked value is not attacker controlled and depends on which invocation writes the entry first. This variant does not require an existing inner cache entry or a slow cache handler and is not covered by the fix for CVE-2026-103004. This issue is fixed in version 16.4.5.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data being read.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | next | >= 16.2.0, <= 16.4.4 | 16.4.5 |
Affected products · Vercel
| Product | Affected versions |
|---|---|
| Next.js | from 16.2.0, before 16.4.5 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/vercel/next.js/security/advisories/GHSA-vc7v-qv4w-wrv8
- https://github.com/vercel/next.js/commit/80c96ede21798d4ad54da12fe50d5b00a09b06e3
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
- https://github.com/advisories/GHSA-vc7v-qv4w-wrv8
- https://nvd.nist.gov/vuln/detail/CVE-2026-119351