Next.js vulnerabilities: known CVEs & security history
Vercel · Web / Framework · 16 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Next.js release lines — 16 in total. 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-2026-44578 | high | 8.6 | 39% | 2026 |
| CVE-2026-64642 | high | 8.2 | 1% | 2026 |
| CVE-2026-44574 | high | 8.1 | 0% | 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-2026-64649 | medium | 6.5 | 1% | 2026 |
| CVE-2026-64645 | medium | 6.1 | 1% | 2026 |
| CVE-2026-44577 | medium | 5.9 | 1% | 2026 |
| CVE-2026-64648 | medium | 5.4 | 1% | 2026 |
| CVE-2026-64647 | medium | 5.4 | 1% | 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 |
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 16 CVEs for Next.js. 0 are critical-severity and 8 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?
None of Next.js's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Next.js vulnerability?
Among tracked issues, CVE-2026-44578 (HIGH, CVSS 8.6) ranks highest — a Server-side request forgery (SSRF) weakness.
Is Next.js safe to use?
It depends on the version. The latest supported Next.js release (16.2.12) 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.