Complete end-of-life dates, support windows, and security status for all Nginx versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.15 | Apr 12, 2011 | Apr 23, 2012 | 5129 days past EOL | EOL |
| 1.2 | 1.2.9 | Apr 23, 2012 | Apr 24, 2013 | 4763 days past EOL | EOL |
| 1.4 | 1.4.7 | Apr 24, 2013 | Apr 24, 2014 | 4398 days past EOL | EOL |
| 1.6 | 1.6.3 | Apr 24, 2014 | Apr 21, 2015 | 4036 days past EOL | EOL |
| 1.8 | 1.8.1 | Apr 21, 2015 | Apr 26, 2016 | 3665 days past EOL | EOL |
| 1.10 | 1.10.3 | Apr 26, 2016 | Apr 12, 2017 | 3314 days past EOL | EOL |
| 1.12 | 1.12.2 | Apr 12, 2017 | Apr 17, 2018 | 2944 days past EOL | EOL |
| 1.14 | 1.14.2 | Apr 17, 2018 | Apr 23, 2019 | 2573 days past EOL | EOL |
| 1.16 | 1.16.1 | Apr 23, 2019 | Apr 20, 2020 | 2210 days past EOL | EOL |
| 1.18 | 1.18.0 | Apr 21, 2020 | Apr 20, 2021 | 1845 days past EOL | EOL |
| 1.19 | 1.19.10 | May 26, 2020 | May 25, 2021 | 1810 days past EOL | EOL |
| 1.20 | 1.20.2 | Apr 20, 2021 | May 24, 2022 | 1446 days past EOL | EOL |
| 1.21 | 1.21.6 | May 25, 2021 | Jun 21, 2022 | 1418 days past EOL | EOL |
| 1.22 | 1.22.1 | May 24, 2022 | Apr 11, 2023 | 1124 days past EOL | EOL |
| 1.23 | 1.23.4 | Jun 21, 2022 | May 23, 2023 | 1082 days past EOL | EOL |
| 1.24 | 1.24.0 | Apr 11, 2023 | Apr 23, 2024 | 746 days past EOL | EOL |
| 1.25 | 1.25.5 | May 23, 2023 | May 29, 2024 | 710 days past EOL | EOL |
| 1.26 | 1.26.3 | Apr 23, 2024 | Apr 23, 2025 | 381 days past EOL | EOL |
| 1.27 | 1.27.5 | May 28, 2024 | Jun 24, 2025 | 319 days past EOL | EOL |
| 1.28 | 1.28.3 | Apr 23, 2025 | Apr 14, 2026 | 25 days past EOL | EOL |
| 1.29 | 1.29.8 | Jun 24, 2025 | Already EOL | Supported | Active |
| 1.30 | 1.30.0 | Apr 14, 2026 | Already EOL | Supported | Active |
When a Nginx 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 Nginx 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 →