Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
Self-hosted Next.js applications that use the Pages Router with statically generated (SSG) or incrementally regenerated (ISR) pages can have a page's cache entry replaced with content from a different route, causing the affected page to serve wrong content to every visitor until the entry is revalidated. Applications deployed on Vercel are not affected.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-94543US | medium5.3 | — | ||
Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, self-hosted applications using the Pages Router with statically generat… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/vercel/next.jsPACKAGE
- https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8WEB
- https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52WEB
- https://github.com/vercel/next.js/releases/tag/v15.5.27WEB
- https://github.com/vercel/next.js/releases/tag/v16.3.8WEB
- https://github.com/vercel/next.js/security/advisories/GHSA-4jqv-mc3x-m676WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-94543ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan