Next.js has cache poisoning of SSG and ISR pages in self-hosted applications

MEDIO 5.3CVE-2026-94543 · GHSA-4jqv-mc3x-m676 · Published 02/10/2026 · updated 06/10/2026

Package	Affected versions	Patched versions
next.js vercel	`≥ 15.0.0, < 15.5.27≥ 16.0.0, < 16.3.8`	`15.5.2716.3.8`
next npm	`≥ 15.0.0, < 15.5.27≥ 16.0.0, < 16.3.8`	`15.5.2716.3.8`

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.

NVD 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.

References

vercel/next.js security advisory · WEB
nvd.nist.gov/vuln/detail/CVE-2026-94543 · ADVISORY
vercel/next.js commit 52c94ab · WEB
vercel/next.js commit 719e4c6 · WEB
vercel/next.js · PACKAGE
vercel/next.js release v15.5.27 · WEB
vercel/next.js release v16.3.8 · WEB

Running one of these products? Scan your site to see whether it exposes a vulnerable version.

Scan my site free

Package

Affected versions

Patched versions

next.js

vercel

≥ 15.0.0, < 15.5.27≥ 16.0.0, < 16.3.8

15.5.2716.3.8

npm

≥ 15.0.0, < 15.5.27≥ 16.0.0, < 16.3.8

15.5.2716.3.8

Description

NVD description