Quick answers
- Is CVE-2026-94482 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94482 being exploited in the wild.
- How severe is CVE-2026-94482?
- High severity, with a CVSS score of 4, published 22 October 2026.
- Which products and versions are affected?
- next (npm) >= 13.0.0, <= 15.5.27, SEMVER:introduced=13.0.0,fixed=15.5.28; Vercel Next.js >= 13.0.0, <= 15.5.27 and >= 16.0.0, <= 16.4.0.
- Is there a fix for CVE-2026-94482?
- Yes. next (npm): upgrade to 15.5.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94482 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-94482?
- Check whether you run next (npm) or Vercel Next.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- next (npm): upgrade to 15.5.28 or later
npm install next@15.5.28
Technical details
A resource exhaustion vulnerability in Next.js App Router triggers excessive CPU usage when processing crafted requests against applications using Server Actions (CWE-770). The attack is network-based, requires no authentication or user interaction, but needs the application to have Server Actions enabled. An attacker can cause denial of service by blocking further request processing in the affected process.
Affected products
- Vercel Next.js >= 13.0.0, <= 15.5.27 and >= 16.0.0, <= 16.4.0
Identifiers
- CVE-2026-94482
- GHSA-p3m5-59mp-jv5r
Timeline
- 2026-10-14: disclosed
- 2026-10-22: advisory
- 2026-10-22: patched