CVE-2026-94484

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

State
Published
Severity
6.3 Medium
Published
Oct 2, 2026
Updated
Oct 5, 2026
Reserved
Sep 21, 2026

Read the record on cve.org

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, applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes can use a shared response cache key that is insufficiently scoped to the source route. A single unauthenticated crafted request can poison that cache, causing cross-user content substitution or persistent denial of service until the poisoned entry is revalidated or replaced. This issue is fixed in versions 15.5.27 and 16.3.8.

Scores

CVSSScoreVectorSource
4.06.3 MediumCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-524 Use of Cache Containing Sensitive Information

Affected Products

ProductVersions
next.jsvercel
  • >= 15.0.0, < 15.5.27Affected
  • >= 16.0.0, < 16.3.8Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.