CVE-2026-64641: Next.js: Denial of Service in App Router using Server Actions

Published Jul 22, 2026
·
Updated

Impact

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.

Workarounds

No workaround exists besides upgrading. Applications using Pages Router or not using Server Actions are not vulnerable.

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, 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.

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

Event History

Jul 22, 2026
Advisory Published
via GitHub·10:59 PM
Data Sourced
via GitHub·10:59 PM
DescriptionWeaknessAffected Software
Jul 27, 2026
CVE Published
via MITRE·05:40 PM
Data Sourced
via MITRE·05:40 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 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-64641?

CVE-2026-64641 has a risk score of 48.

2

What applications are affected by CVE-2026-64641?

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

3

How can I mitigate the effects of CVE-2026-64641?

There are no workarounds for CVE-2026-64641; the only mitigation is to upgrade the application.

4

What impact does CVE-2026-64641 have on my application?

CVE-2026-64641 can lead to excessive CPU usage, which blocks the processing of further requests in the same process.

5

When was CVE-2026-64641 published?

CVE-2026-64641 was published on July 22, 2026.

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