Next.js <16.4.5 Cache Key Confusion via useCache (binary args)
CVE-2026-119349 Published on November 16, 2026
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.4.5, Next.js App Router applications that pass binary arguments, such as Uint8Array or Blob values, to functions using the 'use cache' directive can generate identical cache keys for distinct arguments. Requests with different binary arguments can therefore share a cached result, causing cross-user disclosure of cached data or allowing one request to poison results returned to another user. This issue is fixed in version 16.4.5.
Vulnerability Analysis
CVE-2026-119349 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.
Weakness Type
Use of Multiple Resources with Duplicate Identifier
The software uses multiple resources that can have the same identifier, in a context in which unique identifiers are required. If the software assumes that each resource has a unique identifier, the software could operate on the wrong resource if attackers can cause multiple resources to be associated with the same identifier.
Products Associated with CVE-2026-119349
Want to know whenever a new CVE is published for Vercel Next Js? stack.watch will email you.
Affected Versions
vercel next.js Version >= 16.0.0, < 16.4.5 is affected by CVE-2026-119349Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.