CVE-2026-119790

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

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.3.0 until 16.4.5, Next.js applications using the same 'use cache' function directly during rendering and through unstable_cache() can disclose cached data across root params when that function reads a root param. During the first fill after a cold process start, cross-request deduplication allows a concurrent unstable_cache() request to join the direct call's in-flight fill and receive its result before the root param mismatch is rejected. unstable_cache() then persists that result under a key that omits root params, causing later requests for other root param values to receive the same entry until revalidation or eviction. Exploitation requires the unstable_cache() request to arrive while the first fill is in flight. Outside this race, nesting 'use cache' inside unstable_cache() raises an unsupported-operation error, and avoiding that nesting prevents the issue. This issue is fixed in version 16.4.5.

Analysis

AI-generated

Technical impact

The flaw is a race condition that enables a malicious request to read cached data from another request that carries a different root parameter. During a cold start, the first use of a cached value can be co‑opted by a second concurrent call that reaches the unstable_cache() wrapper while the initial fill is still in flight. Because the cache key does not include the root param, the result is stored under a generic key and subsequent requests for other root param values retrieve the same data. The impact is the inadvertent exposure of sensitive cached information, potentially leaking data between unrelated users. This weakness falls under CWE‑362 Race Condition.

Affected Systems

Vercel’s Next.js framework versions 16.3.0 through 16.4.5 are affected. The vulnerability exists in the internal use of a 'use cache' function during rendering when accessed via unstable_cache(). No other front‑end or back‑end components are mentioned as vulnerable.

Risk and Exploitability

The risk is moderate because the vulnerability can be abused through concurrent HTTP requests, but it requires precise timing and does not provide arbitrary code execution. The CVSS score is 6.3, EPSS is not available, and the issue is not in KEV. Provided the application exposes sensitive cached data, the potential impact is the inadvertent leakage of that data to other users. The race can be triggered by a legitimate request from an attacker with sufficient control over the root parameter. If the application developer is unable to control the request timing, mitigating via code changes or upgrading to the fixed version is recommended.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Next.js package to v16.4.5 or later, where the cache key handling bug is resolved.
  • Refactor the application to eliminate nested calls to 'use cache' within unstable_cache() calls; the API will raise an unsupported‑operation error in this case, effectively preventing the data leak.
  • Implement cache keying that incorporates relevant request parameters or configure explicit eviction/revalidation policies to prevent stale cross‑param data from being served.

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-mfr8-8qww-v76h Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
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.3.0 until 16.4.5, Next.js applications using the same 'use cache' function directly during rendering and through unstable_cache() can disclose cached data across root params when that function reads a root param. During the first fill after a cold process start, cross-request deduplication allows a concurrent unstable_cache() request to join the direct call's in-flight fill and receive its result before the root param mismatch is rejected. unstable_cache() then persists that result under a key that omits root params, causing later requests for other root param values to receive the same entry until revalidation or eviction. Exploitation requires the unstable_cache() request to arrive while the first fill is in flight. Outside this race, nesting 'use cache' inside unstable_cache() raises an unsupported-operation error, and avoiding that nesting prevents the issue. This issue is fixed in version 16.4.5.
Title Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
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:13 PM
Reserved
Oct 30, 2026, 4:28 PM
Status
Awaiting Analysis
Published
Nov 16, 2026, 7:17 PM
Modified
Nov 16, 2026, 8:37 PM