CVE-2026-94484
Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service
CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th
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.
| CWE | CWE-524 |
| Vendor | vercel |
| Product | next.js |
| Published | Oct 2, 2026 |
Stay Ahead of the Next One
Get instant alerts for vercel next.js
Be the first to know when new unknown vulnerabilities affecting vercel next.js are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
vercel / next.js
>= 15.0.0, < 15.5.27 >= 16.0.0, < 16.3.8
References
github.com: https://github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p github.com: https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8 github.com: https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52 github.com: https://github.com/vercel/next.js/releases/tag/v15.5.27 github.com: https://github.com/vercel/next.js/releases/tag/v16.3.8