Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications

These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.

CVE-2026-94543 · Microsoft / collected KEV context

EUVD-2026-91670

GHSA-4jqv-mc3x-m676

cve-program · CVE-2026-94543

• https://github.com/vercel/next.js/security/advisories/GHSA-4jqv-mc3x-m676
• 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

euvd · EUVD-2026-91670

• https://github.com/vercel/next.js/security/advisories/GHSA-4jqv-mc3x-m676
• 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

nvd · 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/vercel/next.js/security/advisories/GHSA-4jqv-mc3x-m676

osv · GHSA-4jqv-mc3x-m676

• 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
• https://github.com/vercel/next.js/releases/tag/v15.5.27
• https://github.com/vercel/next.js/releases/tag/v16.3.8

No related operational record is retained in the current change model.