next
Affected
- introduced
14.2.0, fixed15.5.16(semver)
Fixed versions
15.5.16
Fix
- Fixed version
15.5.16npm install [email protected]
Advisory
Also known as: CVE-2026-44576
Next.js vulnerable to cache poisoning in React Server Component responses
Impact
Applications using React Server Components can be vulnerable to cache poisoning when shared caches do not correctly partition response variants. Under affected conditions, an attacker can cause an RSC response to be served from the original URL and poison shared cache entries so later visitors receive component payloads instead of the expected HTML.
Fix
We now validate and interpret RSC request headers consistently across request classification and rendering, and we enforce the intended cache-busting behavior so RSC payloads are not unexpectedly served from the original URL.
Workarounds
If you cannot upgrade immediately, ensure your CDN or reverse proxy keys on the relevant RSC request headers and honors Vary, or disable shared caching for affected App Router and RSC responses.
Medium Basis: The source's own band: MODERATE
14.2.0, fixed 15.5.16 (semver)15.5.16
15.5.16npm install [email protected]16.0.0, fixed 16.2.5 (semver)16.2.5
16.2.5npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0