Next.js is a React framework for building full-stack web applications. In versions 13.0.0 through 15.5.20 and 16.0.0 through 16.2.10, crafted requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive CPU usage blocking processing of further requests in the same process. This issue has been fixed in versions 15.5.21 and 16.2.11.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/vercel/next.js/commit/019628571641dec57aaf349ba0c360e3964e6f12 Patch
- https://github.com/vercel/next.js/pull/96013 Issue Tracking, Patch
- https://github.com/vercel/next.js/security/advisories/GHSA-m99w-x7hq-7vfj Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.2 · vercelNVD modified 2026-10-24 13:10
Affected (CPE criteria) 1
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
References 5
- https://github.com/vercel/next.js/commit/019628571641dec57aaf349ba0c360e3964e6f12 Patch
- https://github.com/vercel/next.js/pull/96013 Issue Tracking, Patch
- https://github.com/vercel/next.js/releases/tag/v15.5.21 Product, Release Notes
- https://github.com/vercel/next.js/releases/tag/v16.2.11 Product, Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-m99w-x7hq-7vfj Vendor Advisory