CVE-2026-44582
Next.js: Next.js: Cache poisoning allows incorrect response delivery
Severity
LowRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · May 14, 2026
Updated · July 5, 2026
Description
A flaw was found in Next.js. React Server Component responses are vulnerable to cache poisoning in deployments that use shared caches without proper response partitioning. An attacker can exploit collisions in the _rsc cache-busting value to poison cache entries. This allows users to receive incorrect response variants for a given URL, potentially leading to information integrity issues.
Statement
Low: This flaw in Next.js affects deployments utilizing shared caches without adequate response partitioning. An attacker could leverage collisions in the _rsc cache-busting mechanism to poison cache entries, resulting in users receiving unintended content for a given URL. This issue primarily impacts the integrity of cached responses in specific deployment configurations.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
CVSS / CWE
CVSS 3.1 · 3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CWE-354 · Improper Validation of Integrity Check Value