GHSA-vfv6-92ff-j949
Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting
En bref
- Publiée
- Mise à jour
- CVE
- CVE-2026-44582
- CVSS_V3
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Description
### 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.
Paquets affectés
| Paquet | Versions |
|---|---|
| npm · next | introduced 13.4.6, fixed 15.5.16 |
| npm · next | introduced 16.0.0, fixed 16.2.5 |
Références
- https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949 WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-44582 ADVISORY
- https://github.com/vercel/next.js PACKAGE
- https://github.com/vercel/next.js/releases/tag/v15.5.16 WEB
- https://github.com/vercel/next.js/releases/tag/v16.2.5 WEB
Sources
| Source | Licence |
|---|---|
| OSV.dev | CC-BY 4.0 — GitHub Advisory Database |