CVE-2026-119351: Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.4.5
Event History
Frequently Asked Questions
Which applications are exposed to this issue?
Applications using Next.js versions from 16.2.0 through 16.4.5 with Cache Components enabled are affected when an outer 'use cache' function contains a nested 'use cache' call that reads a root parameter through next/root-params and returns a value containing pending promises.
What conditions are needed for the cache leak to occur?
The nested cached call must read a root parameter and return a value with pending promises, allowing React Flight to deliver ready data before the inner cache publishes its root-parameter dependencies. No pre-existing inner cache entry or slow cache handler is required.
What is the impact of a successful trigger?
An outer cache entry can be persisted without the root parameter in its key, so the value written first may be returned for requests using other root parameter values. That outer entry can also ignore nested cache-tag invalidation and cache lifetimes; the leaked value is not attacker controlled.
What should teams do to remediate the issue?
Update Next.js to version 16.4.5, which fixes this issue. The earlier fix for CVE-2026-103004 does not cover this variant.