CVE-2026-945436.3MediumCWE-524

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

vercel · next.js

Affected: vercel next.js · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days

43rd percentile

050100

Higher than 43% of scored CVEs

6.3MediumCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

vercel · next.js>= 15.0.0, < 15.5.27; >= 16.0.0, < 16.3.8

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of Cache Containing Sensitive Information · Information Disclosure
Vendor: vercel
Published: October 2026
Band: Unlikely (under 1%), October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-94543 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.