NGINX End of Life (EOL) Dates & Support Timeline
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 | 5174 days past EOL | EOL |
| 1.2 | 1.2.9 | Apr 23, 2012 | Apr 24, 2013 | 4808 days past EOL | EOL |
| 1.4 | 1.4.7 | Apr 24, 2013 | Apr 24, 2014 | 4443 days past EOL | EOL |
| 1.6 | 1.6.3 | Apr 24, 2014 | Apr 21, 2015 | 4081 days past EOL | EOL |
| 1.8 | 1.8.1 | Apr 21, 2015 | Apr 26, 2016 | 3710 days past EOL | EOL |
| 1.10 | 1.10.3 | Apr 26, 2016 | Apr 12, 2017 | 3359 days past EOL | EOL |
| 1.12 | 1.12.2 | Apr 12, 2017 | Apr 17, 2018 | 2989 days past EOL | EOL |
| 1.14 | 1.14.2 | Apr 17, 2018 | Apr 23, 2019 | 2618 days past EOL | EOL |
| 1.16 | 1.16.1 | Apr 23, 2019 | Apr 20, 2020 | 2255 days past EOL | EOL |
| 1.18 | 1.18.0 | Apr 21, 2020 | Apr 20, 2021 | 1890 days past EOL | EOL |
| 1.19 | 1.19.10 | May 26, 2020 | May 25, 2021 | 1855 days past EOL | EOL |
| 1.20 | 1.20.2 | Apr 20, 2021 | May 24, 2022 | 1491 days past EOL | EOL |
| 1.21 | 1.21.6 | May 25, 2021 | Jun 21, 2022 | 1463 days past EOL | EOL |
| 1.22 | 1.22.1 | May 24, 2022 | Apr 11, 2023 | 1169 days past EOL | EOL |
| 1.23 | 1.23.4 | Jun 21, 2022 | May 23, 2023 | 1127 days past EOL | EOL |
| 1.24 | 1.24.0 | Apr 11, 2023 | Apr 23, 2024 | 791 days past EOL | EOL |
| 1.25 | 1.25.5 | May 23, 2023 | May 29, 2024 | 755 days past EOL | EOL |
| 1.26 | 1.26.3 | Apr 23, 2024 | Apr 23, 2025 | 426 days past EOL | EOL |
| 1.27 | 1.27.5 | May 28, 2024 | Jun 24, 2025 | 364 days past EOL | EOL |
| 1.28 | 1.28.3 | Apr 23, 2025 | Apr 14, 2026 | 70 days past EOL | EOL |
| 1.29 | 1.29.8 | Jun 24, 2025 | May 13, 2026 | 41 days past EOL | EOL |
| 1.30 | 1.30.3 | Apr 14, 2026 | TBD | Supported | Active |
| 1.31 | 1.31.2 | May 13, 2026 | TBD | Supported | Active |
What does NGINX end of life mean for your organization?
When a version of NGINX 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL NGINX versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →