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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| vercel | next.js | >= 15.0.0, < 15.5.27; >= 16.0.0, < 16.3.8 |
References
- https://github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8Patch
- https://github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52Patch
- https://github.com/vercel/next.js/releases/tag/v15.5.27Release Notes
- https://github.com/vercel/next.js/releases/tag/v16.3.8Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-mcj8-r9mp-w47pVendor Advisory
Timeline
- Published
- Oct 2, 2026
- Last modified
- Oct 5, 2026
- NVD status
- Analyzed