Vulnerability · Published May 13, 2026 · Assigned by GitHub_M
CVE-2026-44582Next.js: Cache poisoning via collisions in React Server Component cache-busting
Low 3.7
In plain English
A low-severity security flaw in next.js from vercel. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | next | 15.5.16 | GHSA-vfv6-92ff-j949 |
| npm | next | 16.2.5 | GHSA-vfv6-92ff-j949 |
Affected products (as reported)
Weakness: CWE-328 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
References
- https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949 x_refsource_CONFIRM