Complete end-of-life dates, support windows, and security status for all Nextjs versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9 | 9.5.5 | Jul 8, 2019 | Oct 27, 2020 | 2020 days past EOL | EOL |
| 10 | 10.2.3 | Oct 27, 2020 | Jun 15, 2021 | 1789 days past EOL | EOL |
| 11 | 11.1.4 | Jun 15, 2021 | Jan 27, 2022 | 1563 days past EOL | EOL |
| 12 | 12.3.7 | Oct 26, 2021 | Nov 21, 2022 | 1265 days past EOL | EOL |
| 13 | 13.5.11 | Oct 25, 2022 | Dec 21, 2024 | 504 days past EOL | EOL |
| 14 LTS | 14.2.35 | Oct 26, 2023 | Oct 26, 2025 | 195 days past EOL | EOL |
| 15 LTS | 15.5.18 | Oct 21, 2024 | Oct 21, 2026 | 165 days remaining | Warning |
| 16 LTS | 16.2.6 | Oct 22, 2025 | Already EOL | Supported | Active |
When a Nextjs version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Nextjs should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →