GitHub Advisoryadvisory · npm
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
MEDIUM
Official page ↗
- Aliases
- CVE-2026-94484
- Ecosystem
- npm
- Packages
- next
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
- Weaknesses
- CWE-524
- Reviewed
- 2026-10-07
Affected packages
• npm next: >= 16.0.0, < 16.3.8 → fixed in 16.3.8
• npm next: >= 15.0.0, < 15.5.27 → fixed in 15.5.27
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.
Related
Alias · CVE (1)
- CVE-2026-94484 Next.js is a React framework for building full-stack web applications. vulnerability
Weakness · CWE (1)
- CWE-524 Use of Cache Containing Sensitive Information weakness
References
- https://github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p web
- https://nvd.nist.gov/vuln/detail/CVE-2026-94484 advisory
- https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8 web
- https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52 web
- https://github.com/vercel/next.js package
- https://github.com/vercel/next.js/releases/tag/v15.5.27 web
- https://github.com/vercel/next.js/releases/tag/v16.3.8 web