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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 3.7 · vercelNVD modified 2026-10-26 14:10
Affected (CPE criteria) 1
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
References 1
- https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949 Mitigation, Vendor Advisory