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
vercel: next.js
References1
- github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j9… MitigationVendor Advisory
Metrics
- CVSS 3.1
-
3.7
LOW
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - EPSS — exploit probability
- 0% percentile: 12 · as of 14 November 2026
- CWE
- CWE-328
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.