vercel/next.js · Security
Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
- GHSA ID
- GHSA-4jqv-mc3x-m676
- CVE ID
- CVE-2026-94543
- Severity
- medium
- Published
- Updated
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CVSS v3
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CVSS v4
- 6.3 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Description
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.
CWEs
- CWE-524 · Use of Cache Containing Sensitive Information
References
- https://github.com/vercel/next.js/security/advisories/GHSA-4jqv-mc3x-m676 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2026-94543 ↗
- 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 ↗
- https://github.com/advisories/GHSA-4jqv-mc3x-m676 ↗