CVE-2026-94484

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

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

Weaknesses (CWE)

• CWE-524

Advisories

• 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

European references

• ENISA EUVD · EUVD-2026-91674
• GCVE · GCVE-0-2026-94484

Affected configurations (NVD CPE)

• cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* ≥ 15.0.0 < 15.5.27
• cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* ≥ 16.0.0 < 16.3.8

Affected products

References

• https://github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p
• https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8
• https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52
• https://github.com/vercel/next.js/releases/tag/v15.5.27
• https://github.com/vercel/next.js/releases/tag/v16.3.8

Sources