Advisory

GHSA-wfc6-r584-vfw7

Also known as: CVE-2026-44576

Summary

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

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-11 15:54 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

next

npm · All systems

Affected

  • introduced 14.2.0, fixed 15.5.16 (semver)

Fixed versions

15.5.16

Fix

next

npm · All systems

Affected

  • introduced 16.0.0, fixed 16.2.5 (semver)

Fixed versions

16.2.5

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences