Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 16 Nov 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 16 Nov 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vercel
Vercel next.js |
|
| Vendors & Products |
Vercel
Vercel next.js |
Mon, 16 Nov 2026 18:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-16T19:00:23.285Z
Reserved: 2026-10-29T20:44:30.287Z
Link: CVE-2026-119349
Updated: 2026-11-16T19:00:15.569Z
Status : Awaiting Analysis
Published: 2026-11-16T19:17:27.007
Modified: 2026-11-16T20:37:04.673
Link: CVE-2026-119349
No data.
OpenCVE Enrichment
Updated: 2026-11-16T20:30:22Z