Vulnerability Description
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 generated or Incremental Static Regeneration pages can key a response cache entry without sufficiently binding it to the source route. A request can replace one page's cache entry with content from a different route, causing the affected page to serve incorrect content to every visitor until revalidation. Applications deployed on Vercel are not affected. This issue is fixed in versions 15.5.27 and 16.3.8.
Related Weaknesses (CWE)
References
- https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b
- https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a5
- 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
FAQ
What is CVE-2026-94543?
CVE-2026-94543 is a documented vulnerability. 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 generated or Incremental St...
How severe is CVE-2026-94543?
CVSS scoring is not yet available for CVE-2026-94543. Check NVD for updates.
Is there a patch for CVE-2026-94543?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.