Vulnerability in Vercel Next.js
CVE-2026-94484
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.
Published · last modified .
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Vercel Next.js — versions >= 15.0.0, < 15.5.27, >= 16.0.0, < 16.3.8
Weakness classification (CWE)
References
- github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p
- github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8
- github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52
- github.com/vercel/next.js/releases/tag/v15.5.27
- github.com/vercel/next.js/releases/tag/v16.3.8