CVE-2026-64646: Next.js: Unbounded Server Action payload in Edge runtime

Published Jul 22, 2026
·
Updated

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.

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
npm/next>=16.0.0<16.2.11
16.2.11
npm/next>=13.0.0<15.5.21
15.5.21
Vercel Next.js Node.js>=13.0.0<15.5.21
Vercel Next.js Node.js>=16.0.0<16.2.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/next to a version that resolves this vulnerability.

    Fixed in 16.2.11
  2. Upgrade

    Upgrade npm/next to a version that resolves this vulnerability.

    Fixed in 15.5.21
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.5.21
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.2.11
  5. Configuration

    If you cannot upgrade, ensure your hosting provider limits the request's body size to 5 MiB at maximum.

    Hosting provider / Next.js application (request body size) Maximum request body size = 5 MiB (max)

Event History

Jul 22, 2026
Advisory Published
via GitHub·11:02 PM
Data Sourced
via GitHub·11:02 PM
DescriptionWeaknessAffected Software
Jul 27, 2026
CVE Published
via MITRE·06:54 PM
Data Sourced
via MITRE·06:54 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-64646?

The severity of CVE-2026-64646 is rated at 29.

2

How do I fix CVE-2026-64646?

To fix CVE-2026-64646, upgrade your Next.js application to the latest version.

3

What is the impact of CVE-2026-64646 on Next.js applications?

CVE-2026-64646 can lead to excessive memory consumption in Next.js applications using the Edge runtime with Server Actions.

4

What can I do if I cannot upgrade to fix CVE-2026-64646?

If you cannot upgrade, ensure your hosting provider limits the request's body size to mitigate CVE-2026-64646.

5

Which version of Next.js is affected by CVE-2026-64646?

CVE-2026-64646 affects Next.js applications utilizing the App Router with at least one Server Action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203