CVE-2026-119351

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

Published Nov 16, 2026 CVSS 4.0 · 6.3 Medium EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Next.js applications that enable Cache Components suffer from a concurrency flaw (CWE-362) that creates a race condition. When a nested use cache call reads a root parameter through next/root-params and returns a value containing pending promises, the outer cache may finish and persist the entry before the inner cache publishes its root‑param dependencies. Because the outer entry is stored under a key that omits the root parameter, the first value written will subsequently be served for all other root parameter values, leaking data that is not attacker‑controlled but depends on invocation order.

Affected Systems

Vulnerable releases include Next.js versions 16.2.0 through 16.4.5 from vercel:next.js. Any server‑side rendered application that uses Cache Components and employs next/root-params within nested use cache calls is affected, independent of the hosting environment.

Risk and Exploitability

The CVSS score of 6.3 indicates medium severity. EPSS is not available, and the vulnerability is not listed in CISA’s KEV catalog, suggesting no widespread exploitation yet. The attack vector is not explicitly defined in the advisory but involves shared cache state that could be influenced through crafted requests or timing attacks. Although the data leaked is not attacker‑controlled, cross‑context contamination can impact confidentiality, maintaining a moderate risk for sensitive applications.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Next.js 16.4.5 or later, which removes the race condition between outer and inner cache entries.
  • Restart the application server so the updated code is loaded and any stale cache is cleared.
  • As a temporary measure, disable Cache Components or avoid using nested use cache calls with next/root-params until the patch is applied.
  • Audit cache key definitions in the application to ensure root‑param dependencies are explicitly included where required.

Generated by OpenCVE AI on November 16, 2026 at 19:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Vendors & Products Vercel
Vercel next.js
Type Values Removed Values Added
Description 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.
Title Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
Weaknesses CWE-362
References
Metrics cvssV4_0

{'score': 6.3, 'vector': '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'}

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 6:27 PM
Reserved
Oct 29, 2026, 8:44 PM
Status
Awaiting Analysis
Published
Nov 16, 2026, 7:17 PM
Modified
Nov 16, 2026, 8:37 PM