CVE-2026-44582: Next.js: Cache poisoning via collisions in React Server Component cache-busting
### 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44582?
CVE-2026-44582 has a medium severity rating due to the potential risk of cache poisoning affecting application responses.
How do I fix CVE-2026-44582?
To mitigate CVE-2026-44582, upgrade Next.js to version 16.2.5 or 15.5.16.
What systems are affected by CVE-2026-44582?
CVE-2026-44582 affects Next.js versions between 13.4.6 and 16.2.5, as well as various Node.js deployments.
What type of vulnerability is CVE-2026-44582?
CVE-2026-44582 is classified as a cache poisoning vulnerability resulting from insufficient response partitioning in React Server Components.
Is CVE-2026-44582 being actively exploited?
There are currently no reported active exploits for CVE-2026-44582, but it is recommended to apply the fix promptly.