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, requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive memory consumption if that Server Actions uses the Edge runtime. 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/57c31f724d746e86a9e8b92aa8be538a922446a4 Patch
- https://github.com/vercel/next.js/commit/9a4651e754f70b12e397694ffc41f44c3ba8cc17 Patch
- https://github.com/vercel/next.js/security/advisories/GHSA-4c39-4ccg-62r3 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 6.3 · 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/57c31f724d746e86a9e8b92aa8be538a922446a4 Patch
- https://github.com/vercel/next.js/commit/9a4651e754f70b12e397694ffc41f44c3ba8cc17 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-4c39-4ccg-62r3 Vendor Advisory