Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4jqv-mc3x-m676

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

CVSS 6.3 MediumEPSS 0.0051 · 43rd percentile

Published by the GitHub Advisory Database at 7 Oct 2026, 20:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
nextnpm>=15.0.0, <15.5.27 || >=16.0.0, <16.3.815.5.27, 16.3.8
Identifiers
GHSA-4jqv-mc3x-m676 · CVE-2026-94543
Weakness (CWE)
CWE-524
Tags
Published
7 Oct 2026
Updated
7 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Next.js versions 15.0.0 up to 15.5.27 (excluding that release) and 16.0.0 up to 16.3.8 (excluding that release) are affected. In self-hosted applications that use the Pages Router with statically generated or incrementally regenerated pages, a page's cache entry can be replaced with content from a different route, so every visitor sees the wrong page until the entry is revalidated. The source does not say what an attacker must do to trigger this, and it states that applications deployed on Vercel are not affected. Upgrade to Next.js 15.5.27 or 16.3.8, which contain fixes.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0051, the 43rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.