Next.js vulnerabilities: known CVEs & security history
Vercel · Web / Framework · 35 tracked CVEs · 1 actively exploited · updated November 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Next.js release lines — 35 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Next.js's current status and the safe version to run.
Known Next.js CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-55182⚡ exploited | critical | 10 | 100% | 2025 |
| CVE-2026-44578 | high | 8.6 | 36% | 2026 |
| CVE-2026-64642 | high | 8.2 | 1% | 2026 |
| CVE-2026-44574 | high | 8.1 | 1% | 2026 |
| CVE-2026-64641 | high | 7.5 | 1% | 2026 |
| CVE-2026-45109 | high | 7.5 | 1% | 2026 |
| CVE-2026-44579 | high | 7.5 | 1% | 2026 |
| CVE-2026-44575 | high | 7.5 | 2% | 2026 |
| CVE-2026-44573 | high | 7.5 | 1% | 2026 |
| CVE-2025-67779 | high | 7.5 | 20% | 2025 |
| CVE-2025-55184 | high | 7.5 | 67% | 2025 |
| CVE-2026-94483 | medium | 6.5 | 0% | 2026 |
| CVE-2026-64649 | medium | 6.5 | 0% | 2026 |
| CVE-2025-57822 | medium | 6.5 | 3% | 2025 |
| CVE-2025-57752 | medium | 6.2 | 0% | 2025 |
| CVE-2026-64645 | medium | 6.1 | 0% | 2026 |
| CVE-2026-44580 | medium | 6.1 | 0% | 2026 |
| CVE-2026-44577 | medium | 5.9 | 1% | 2026 |
| CVE-2026-94486 | medium | 5.4 | 0% | 2026 |
| CVE-2026-64648 | medium | 5.4 | 0% | 2026 |
| CVE-2026-64647 | medium | 5.4 | 0% | 2026 |
| CVE-2026-44576 | medium | 5.4 | 0% | 2026 |
| CVE-2026-94543 | medium | 5.3 | 0% | 2026 |
| CVE-2026-94485 | medium | 5.3 | 0% | 2026 |
| CVE-2026-103004 | medium | 5.3 | 0% | 2026 |
| CVE-2026-64646 | medium | 5.3 | 1% | 2026 |
| CVE-2026-64644 | medium | 5.3 | 1% | 2026 |
| CVE-2026-64643 | medium | 5.3 | 1% | 2026 |
| CVE-2025-55183 | medium | 5.3 | 64% | 2025 |
| CVE-2026-94484 | medium | 4.8 | 0% | 2026 |
| CVE-2026-44581 | medium | 4.7 | 0% | 2026 |
| CVE-2025-55173 | medium | 4.3 | 1% | 2025 |
| CVE-2026-94544 | medium | 4.2 | 0% | 2026 |
| CVE-2026-44582 | low | 3.7 | 0% | 2026 |
| CVE-2026-44572 | low | 3.7 | 0% | 2026 |
Is my Next.js version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Next.js version → · Monitor Next.js for new CVEs →
Next.js vulnerabilities — frequently asked
How many known vulnerabilities does Next.js have?
IsItPatched tracks 35 CVEs for Next.js, 1 of which is actively exploited (CISA KEV). 1 is critical-severity and 10 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Next.js have any actively-exploited vulnerabilities?
Yes — 1 Next.js CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild (1 linked to ransomware). Patch it as a priority.
What is the most severe Next.js vulnerability?
Among tracked issues, CVE-2025-55182 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Insecure deserialization weakness.
Is Next.js safe to use?
It depends on the version. The latest supported Next.js release (16.4.3) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Next.js security status · Next.js end-of-life · actively-exploited CVEs. Always verify against Vercel's advisories — see our disclaimer.