CVE-2026-119349

Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments

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.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.

Analysis

AI-generated

Technical impact

Next.js App Router applications that use the 'use cache' directive can generate identical cache keys when binary arguments such as Uint8Array or Blob values are passed to cacheable functions. This leads to shared cached results for different inputs, enabling one user’s data to be disclosed to or poisoned by another user. The primary impact is a breach of confidentiality and integrity for cached data that should be isolated between users.

Affected Systems

The vulnerability affects the Vercel Next.js framework, specifically versions 16.0.0 through 16.4.5. Systems running any of these releases with App Router enabled and passing binary arguments to cacheable functions are at risk.

Risk and Exploitability

The CVSS base score of 6.3 indicates moderate severity. No EPSS score is available, and the vulnerability is not listed in CISA’s KEV catalog, implying it has not yet been widely exploited in the field. Attackers can trigger the flaw by sending HTTP requests that include binary arguments; the vulnerability can be exploited remotely and does not require elevated privileges. The likely attack vector is a client-side request that includes binary data passed to a cached server-side function, based on the description.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Next.js to version 16.4.5 or later to incorporate the vendor fix.
  • If upgrading immediately is not possible, avoid passing binary arguments to functions marked with the 'use cache' directive.
  • As an interim measure, implement a custom key generation strategy that normalizes binary data so that equivalent inputs do not clash, or disable the cache directive for binary-argument functions.

Generated by OpenCVE AI on November 16, 2026 at 20:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

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.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.
Title Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
Weaknesses CWE-694
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-694

    Use of Multiple Resources with Duplicate Identifier

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 7:00 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