CVE-2026-44582: Next.js: Cache poisoning via collisions in React Server Component cache-busting
vercel · next.js
Affected: vercel next.js · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 11% of scored CVEs
DescriptionCVE.org
Next.js is a React framework for building full-stack web applications. From 13.4.6 to before 15.5.16 and 16.2.5, 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. This vulnerability is fixed in 15.5.16 and 16.2.5.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- vercel · next.js>= 13.4.6, < 15.5.16; >= 16.0.0, < 16.2.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Use of Weak Hash · Cryptography
- Vendor
- vercel
- Published
- May 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-44582 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.