Summary
Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
Advisory details
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
References
- https://github.com/advisories/GHSA-mcj8-r9mp-w47p
- https://github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p
- https://nvd.nist.gov/vuln/detail/CVE-2026-94484
- https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8
- https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52
- https://github.com/vercel/next.js/releases/tag/v15.5.27
- https://github.com/vercel/next.js/releases/tag/v16.3.8
Related vulnerabilities
All Supply chain →- MEDIUMCVE-2026-107851
Contao: Improper access control in the table access voter
- MEDIUMCVE-2026-94544
Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages
- MEDIUMCVE-2026-94543
Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
- MEDIUMCVE-2026-84933
undici vulnerable to cross-user cookie disclosure via Set-Cookie caching in shared caches
- MEDIUMCVE-2026-88059
Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`
- HIGHCVE-2026-96627
Arcane: Delegated users:update permission allows admin account takeover via password reset (no privilege-hierarchy check)