CVE-2026-94484Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service

Description

Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes can use a shared response cache key that is insufficiently scoped to the source route. A single unauthenticated crafted request can poison that cache, causing cross-user content substitution or persistent denial of service until the poisoned entry is revalidated or replaced. This issue is fixed in versions 15.5.27 and 16.3.8.

Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.

Affected products and versions

References and patches

• https://github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p Vendor Advisory
• https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8 Patch
• https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52 Patch
• https://github.com/vercel/next.js/releases/tag/v15.5.27 Release Notes
• https://github.com/vercel/next.js/releases/tag/v16.3.8 Release Notes