CVE-2026-44582 Next.js: Cache poisoning via collisions in React Server Component cache-busting

Low 3.7 Published Updated

Attackers can poison shared caches in Next.js deployments, causing users to receive incorrect response variants for specific URLs.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-44582?

CVE-2026-44582 is a low-severity vulnerability in Vercel Next.js, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-328

Which versions are affected by CVE-2026-44582?

4 open source packages ship an affected version, including next. It affects 1 product.

PackageAffectedFixed in
next npmFrom 13.4.615.5.16
next npmFrom 13.4.615.5.16
next npmFrom 16.0.016.2.5
next npmFrom 16.0.016.2.5

Products include Vercel Next.js.

How do I fix CVE-2026-44582?

Upgrade next to a fixed version for your release line: 15.5.16 or 16.2.5.

Is CVE-2026-44582 being exploited?

There is no known exploitation of CVE-2026-44582 in the wild and no public exploit code.

All Vercel Next.js vulnerabilities

Sources

Also known as CLEANSTART-2026-AV98689, CLEANSTART-2026-MX70977, GHSA-vfv6-92ff-j949, MINI-3qj5-8pw8-5pqg, MINI-frw4-pg6m-w298, MINI-rc89-mjhp-gvj3 and 2 more.

Is CVE-2026-44582 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free