Back

LOW

Next.js: Cache poisoning via collisions in React Server Component cache-busting

Published May 13, 2026

Description

Next.js is a React framework for building full-stack web applications. From 13.4.6 to before 15.5.16 and 16.2.5, React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL. This vulnerability is fixed in 15.5.16 and 16.2.5.

Affected products

Remediation

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

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

Weaknesses (2)

References (8)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner GitHub_M
Published May 13, 2026
Updated May 14, 2026
Reserved May 6, 2026
CISA Vulnrichment
Updated May 14, 2026
NVD
Status Analyzed
Modified Jun 17, 2026
Red Hat
Severity Low
Public date May 13, 2026
GHSA-VFV6-92FF-J949