CVE-2026-119349
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
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.
INFO
Published Date :
Nov. 16, 2026, 6:39 p.m.
Last Modified :
Nov. 16, 2026, 6:39 p.m.
Remotely Exploit :
No
Source :
GitHub_M
Solution
- Update Next.js to version 16.4.5 or later.
- Ensure binary arguments are handled correctly.
- Review cache invalidation logic.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-119349 vulnerability anywhere in the article.