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


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** CLEANSTART-2026-TE57560, ECHO-7955-3140-c50d, GHSA-p3m5-59mp-jv5r, ROOT-APP-NPM-CVE-2026-94482

## What is CVE-2026-94482?

CVE-2026-94482 is a high-severity vulnerability in vercel next.js, published on 22 Oct 2026. 

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-94482?

4 open source packages ship an affected version, including next.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 13.0.0 | 15.5.28 |
| `next` | npm | From 13.0.0 | 15.5.28 |
| `next` | npm | From 16.0.0 | 16.4.1 |
| `next` | npm | From 16.0.0 | 16.4.1 |

## How do I fix CVE-2026-94482?

Upgrade next to a fixed version for your release line: 15.5.28 or 16.4.1.

## Is CVE-2026-94482 being exploited?

There is no known exploitation of CVE-2026-94482 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94482 and fix it if it is affected.

What it is: CVE-2026-94482 is a high-severity vulnerability in vercel next.js, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94482 in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 13.0.0; fixed in 15.5.28
- next (npm): affected from 13.0.0; fixed in 15.5.28
- next (npm): affected from 16.0.0; fixed in 16.4.1
- next (npm): affected from 16.0.0; fixed in 16.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94482/ (Markdown: https://insights.sbomify.com/CVE-2026-94482/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94482
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94482
- OSV: https://osv.dev/vulnerability/CVE-2026-94482

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94482/
Summaries are generated and may contain mistakes; the official description above is the record.