Skip to content
Web

CVE-2026-94482

8.2
High
EPSS 0.36%Patch availableOct 24, 2026

Next.js Server Actions can be abused to exhaust CPU and block requests (DoS).

common questions

Is CVE-2026-94482 being exploited?

Not confirmed. CVE-2026-94482 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-94482?

CVE-2026-94482 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-94482?

Yes. A fix has been recorded for CVE-2026-94482. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-94482 affect?

CVE-2026-94482 affects Next.js App Router with Server Actions, Next.js >=13.0.0 and <15.5.28 (v15.5.28 fixed), Next.js 16.0.0–16.4.0 (v16.4.1 fixed). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-94482?

Upgrade to Next.js 15.5.28 or 16.4.1; disable Server Actions if immediate patching isn't possible.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Next.js App Router with Server ActionsNext.js >=13.0.0 and <15.5.28 (v15.5.28 fixed)Next.js 16.0.0–16.4.0 (v16.4.1 fixed)
impact

Crafted requests against App Router apps with Server Actions cause excessive CPU use and block processing, causing denial of service.

action required

Patch when possible

affected versions
vercel next.js
  • affected>= 13.0.0 and < 15.5.28
  • affected>= 16.0.0 and < 16.4.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved