Advisory record · GHSA-mcj8-r9mp-w47p

Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service

CVSS 6.3 MediumEPSS 0.0024 · 15th percentile

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

PackageEcosystemAffectedFixed in
nextnpm>=16.0.0, <16.3.8 || >=15.0.0, <15.5.2716.3.8, 15.5.27
Identifiers
GHSA-mcj8-r9mp-w47p · CVE-2026-94484
Weakness (CWE)
CWE-524
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 from 15.0.0 before 15.5.27 and from 16.0.0 before 16.3.8 are affected. Applications that use a root-level catch-all page alongside statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request, with the source indicating this can lead to cross-user content substitution and persistent denial of service. 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.0024, the 15th 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.