CVE-2026-119790
Received Received - Intake

Information Disclosure in Next.js Framework

Vulnerability report for CVE-2026-119790, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-16
AI Q&A
2026-11-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
vercel next.js From 16.3.0 (inc) to 16.4.5 (inc)
vercel next.js 16.4.5

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Next.js versions 16.3.0 to 16.4.4. It involves a race condition where cached data intended for one root parameter value is incorrectly shared with requests for other values. This happens when a 'use cache' function is called both directly during rendering and through the unstable_cache() API during a cold process start. The issue allows unauthorized access to cached data across different root parameters until the cache entry is revalidated or evicted.

Exploitation requires a specific timing condition where an unstable_cache() request arrives while the first cache fill is still in progress. The vulnerability is fixed in Next.js version 16.4.5.

Impact Analysis

This vulnerability could lead to unauthorized disclosure of cached data across different root parameter values. If exploited, an attacker might access sensitive information intended for other users or requests, potentially compromising data confidentiality. The impact is limited to scenarios where the race condition occurs, and the cached data is exposed only until the cache entry is revalidated or evicted.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by potentially exposing sensitive user data to unauthorized parties. GDPR requires protecting personal data, and HIPAA mandates safeguarding protected health information. If exploited, this issue might lead to unauthorized data access, violating these regulations' confidentiality requirements.

Mitigation Strategies

Upgrade Next.js to version 16.4.5 or later to patch the vulnerability. Avoid nesting 'use cache' inside unstable_cache() as a temporary workaround.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119790. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...