MediumGHSA-mcj8-r9mp-w47pCVE-2026-94484
Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
Published 7 Oct 2026 · Updated 7 Oct 2026
Affected packages
nextnpm
- Affected
- >=16.0.0 <16.3.8
- Fixed in
- 16.3.8
Update to the fixed version for your release line, for example:
npm install next@16.3.8nextnpm
- Affected
- >=15.0.0 <15.5.27
- Fixed in
- 15.5.27
Update to the fixed version for your release line, for example:
npm install next@15.5.27Details
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.
Is GHSA-mcj8-r9mp-w47p in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.
References
- Linkgithub.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47p
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-94484
- Linkgithub.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8
- Linkgithub.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v15.5.27
- Linkgithub.com/vercel/next.js/releases/tag/v16.3.8
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.