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

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.

Scores

EPSS (exploitation in 30 days)

0.21% · top 88% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.7.

Weakness

• CWE-328: Use of Weak Hash (opens in a new tab)All about CWE-328 and its CVEs

Affected products

• vercel · next.js

  • affected >= 13.4.6, < 15.5.16
  • affected >= 16.0.0, < 16.2.5

Affected packages

From reviewed advisories of the GitHub Advisory Database.

• npmnextGHSA-vfv6-92ff-j949 (opens in a new tab)

References (1)

• https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949 (opens in a new tab)x_refsource_CONFIRM

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisory GHSA-vfv6-92ff-j949 (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-44582](https://trackcve.app/badge/CVE-2026-44582.svg)](https://trackcve.app/cve/CVE-2026-44582)

Record last updated 14 May 2026, 18:23 UTC.