Next.js Cache Poisoning Vulnerability in React Server Components

Vulnerability

A cache poisoning vulnerability has been identified in Next.js versions 13.4.6 prior to 15.5.16 and 16.0.0 prior to 16.2.5. This issue affects deployments that use shared caches with inadequate response partitioning, allowing an attacker to manipulate cache entries. As a result, users may receive incorrect response variants for specific URLs. The vulnerability arises from collisions in the '_rsc' cache-busting value, which can be exploited to poison cache responses.

Impact

Exploitation of this vulnerability can lead to cache poisoning, where users receive incorrect response variants for a given URL, disrupting the intended functionality of the application.

Remediation

To address this vulnerability, users should upgrade to Next.js versions 15.5.16 or 16.2.5. If an immediate upgrade is not possible, ensure that intermediary caches properly respect the 'Vary' header for RSC-related request headers, or disable shared caching for affected RSC responses until a patched version can be deployed.

Added: May 13, 2026, 7:46 PM
Updated: May 13, 2026, 7:46 PM

Vulnerability Rating

Custom Algorithm
spread
5.2
impact
0.6
exploitability
7.2
remediation
7.9
relevance
8.2
threat
0.0
urgency
2.9
incentive
4.2

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.