All vulnerabilities
CVE-2026-94484GHSA-mcj8-r9mp-w47p

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

vercel nextnpmFrameworks
Open in ThreatlineRecord JSON
CVSS
6.3Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.24%Chance of exploitation activity in the next 30 days, higher than 14% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in16.3.8Also 15.5.27, 16.3.? and 1 moreGitHub
Published2 Oct 2026Updated 7 Oct 2026CVE List

What fixes it

  • 16.3.8next, npmGitHubnpm install next@16.3.8
  • 15.5.27next, npmGitHubnpm install next@15.5.27
  • 16.3.?next, npmGitHubnpm install next@16.3.?
  • 15.5.?next, npmGitHubnpm install next@15.5.?

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.

Text from CVE List

Affected versions 8

  • next, npm>= 16.0.0, < 16.3.8GitHub
  • next, npm>= 15.0.0, < 15.5.27GitHub
  • next.jsaffected: >= 15.0.0, < 15.5.27CVE List
  • next.jsaffected: >= 16.0.0, < 16.3.8CVE List
  • next, npm>= 16.0.0GitHub
  • next, npm>= 15.0.0GitHub
  • next, npmfrom 16.0.0, fixed in 16.3.8OSV
  • next, npmfrom 15.0.0, fixed in 15.5.27OSV

References 7