CVE-2026-119349
Received Received - Intake

Binary Argument Cache Key Collision in Next.js

Vulnerability report for CVE-2026-119349, 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.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.

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.0.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-694 The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Next.js versions 16.0.0 to 16.4.4 have a cache key generation flaw in the 'use cache' directive when handling binary arguments like Uint8Array or Blob. Distinct binary inputs can produce identical cache keys, causing cached results to be shared incorrectly between users. This leads to cross-user disclosure of cached data or cache poisoning where one user's request affects another's.

Detection Guidance

Check if your Next.js application uses the 'use cache' directive with binary arguments like Uint8Array or Blob. Inspect cache keys for identical generation from distinct binary inputs. Review server logs for unexpected cached data sharing between users.

Impact Analysis

This vulnerability allows unauthorized access to cached data intended for other users, potentially exposing sensitive information. It also enables attackers to manipulate cached results, causing incorrect data to be served to users. The impact includes privacy breaches and data integrity issues without requiring special privileges or user interaction.

Compliance Impact

This vulnerability could violate GDPR's data protection requirements by enabling unauthorized access to personal data through cache disclosure. For HIPAA, it may compromise the confidentiality of protected health information if cached medical data is exposed. Organizations using affected Next.js versions risk non-compliance with privacy regulations due to potential data breaches.

Mitigation Strategies

Upgrade Next.js to version 16.4.5 or later. Avoid passing binary arguments to cached functions. Implement input validation to ensure unique cache keys. Monitor cached responses for unauthorized access or data leaks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119349. 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...