~ / search / GHSA-vfv6-92ff-j949

GHSA-vfv6-92ff-j949

Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting

Source: GitHub Advisory Database (reviewed) Low CVE-2026-44582

Packages

EcosystemPackageAffectedFixed in
npm next >= 13.4.6, < 15.5.16 15.5.16
npm next >= 16.0.0, < 16.2.5 16.2.5

Details

As written in the advisory (Markdown source, shown as plain text).

### Impact 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. ### Fix We strengthened the `_rsc` cache-busting mechanism to make practical collisions significantly harder and to better separate response variants that should not share cache entries. ### Workarounds If you cannot upgrade immediately, ensure intermediary caches correctly honor `Vary` for RSC-related request headers, or disable shared caching for affected RSC responses until you can deploy a patched release.

References

External links from the advisory. They lead to third-party sites.