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

Published Oct 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. From 13.0.0 until 15.5.28 and 16.4.1, crafted requests targeting App Router applications with at least one Server Action can cause excessive CPU consumption and block processing of further requests in the same process. Applications using the Pages Router and App Router applications without Server Actions are not affected. This issue is fixed in versions 15.5.28 and 16.4.1.

— MITRE

Affected Software

3 affected componentsFixes available
npm/next>=13.0.0<15.5.28, >=16.0.0<16.4.1
npm/next>=16.0.0<=16.4.0
16.4.1
npm/next>=13.0.0<=15.5.27
15.5.28

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.4.1
  2. Upgrade

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

    Fixed in 15.5.28
  3. Upgrade

    Upgrade Next.js to a version that resolves this vulnerability.

    Fixed in 15.5.28
  4. Upgrade

    Upgrade Next.js to a version that resolves this vulnerability.

    Fixed in 16.4.1

Event History

Oct 22, 2026
CVE Published
via MITRE·03:22 PM
Data Sourced
via MITRE·03:22 PM
DescriptionWeakness
Advisory Published
via GitHub·03:50 PM
Data Sourced
via GitHub·03:50 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

Which applications are affected?

Affected applications use the App Router and have at least one Server Action. Applications that use the Pages Router, or App Router applications with no Server Actions, are not affected.

2

What does an attacker need to exploit this issue?

An attacker needs to send crafted requests to a vulnerable App Router application that has at least one Server Action. Successful exploitation can consume excessive CPU and block further requests handled by the same process.

3

What should teams do to remediate the issue?

Upgrade Next.js to version 15.5.28 or 16.4.1. The issue affects versions from 13.0.0 up to the fixed releases.

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