MediumGHSA-4c39-4ccg-62r3CVE-2026-64646
Next.js: Unbounded Server Action payload in Edge runtime
Published 22 Jul 2026 · Updated 10 Sept 2026
Affected packages
nextnpm
- Affected
- >=13.0.0 <15.5.21
- Fixed in
- 15.5.21
Update to the fixed version for your release line, for example:
npm install next@15.5.21nextnpm
- Affected
- >=16.0.0 <16.2.11
- Fixed in
- 16.2.11
Update to the fixed version for your release line, for example:
npm install next@16.2.11Details
Impact
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
Workarounds
If you cannot upgrade, ensure your hosting provider limits the request's body size. 5 MiB should be allowed at max by your hosting provider.
Is GHSA-4c39-4ccg-62r3 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-4c39-4ccg-62r3
- Linkgithub.com/vercel/next.js/commit/57c31f724d746e86a9e8b92aa8be538a922446a4
- Linkgithub.com/vercel/next.js/commit/9a4651e754f70b12e397694ffc41f44c3ba8cc17
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v15.5.21
- Linkgithub.com/vercel/next.js/releases/tag/v16.2.11
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.