VDB
Sign up
MEDIUM5.4

GHSA-wfc6-r584-vfw7

Next.js vulnerable to cache poisoning in React Server Component responses

Quick fix

GHSA-wfc6-r584-vfw7 — next: upgrade to the fixed version with the command below.

npm install next@15.5.16

Details

### 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.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm/next
Introduced in: 14.2.0Fixed in: 15.5.16
Fixnpm install next@15.5.16
npm/next
Introduced in: 16.0.0Fixed in: 16.2.5
Fixnpm install next@16.2.5

References