Azul Zulu End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Azul Zulu versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7 LTS | 7.56 | Sep 25, 2013 | Jul 31, 2022 | 1423 days past EOL | EOL |
| 6 LTS | N/A | Jan 21, 2014 | Dec 31, 2018 | 2731 days past EOL | EOL |
| 8 LTS | 8.92.0.21 | Apr 8, 2014 | Dec 31, 2030 | 1652 days remaining | Active |
| 9 | 9.0.7.1 | Sep 21, 2017 | Mar 31, 2018 | 3006 days past EOL | EOL |
| 10 | 10.3.5 | Mar 27, 2018 | Sep 30, 2018 | 2823 days past EOL | EOL |
| 11 LTS | 11.86.21 | Sep 25, 2018 | Jan 31, 2032 | 2048 days remaining | Active |
| 12 | 12.3.11 | Mar 19, 2019 | Sep 30, 2019 | 2458 days past EOL | EOL |
| 13 | 13.54.17 | Sep 17, 2019 | Mar 31, 2023 | 1180 days past EOL | EOL |
| 14 | 14.29.23 | Mar 17, 2020 | Sep 30, 2020 | 2092 days past EOL | EOL |
| 15 | 15.46.17 | Sep 15, 2020 | Mar 31, 2023 | 1180 days past EOL | EOL |
| 16 | 16.32.15 | Mar 16, 2021 | Sep 30, 2021 | 1727 days past EOL | EOL |
| 17 LTS | 17.64.17 | Sep 15, 2021 | Sep 30, 2029 | 1195 days remaining | Active |
| 18 | 18.32.13 | Mar 12, 2022 | Sep 30, 2022 | 1362 days past EOL | EOL |
| 19 | 19.32.13 | Sep 20, 2022 | Mar 31, 2023 | 1180 days past EOL | EOL |
| 20 | 20.32.11 | Mar 21, 2023 | Sep 19, 2023 | 1008 days past EOL | EOL |
| 21 LTS | 21.48.17 | Sep 19, 2023 | Sep 30, 2031 | 1925 days remaining | Active |
| 22 | 22.32.15 | Mar 19, 2024 | Sep 17, 2024 | 644 days past EOL | EOL |
| 23 | 23.32.11 | Sep 17, 2024 | Mar 18, 2025 | 462 days past EOL | EOL |
| 24 | 24.32.13 | Mar 18, 2025 | Sep 16, 2025 | 280 days past EOL | EOL |
| 25 LTS | 25.32.21 | Sep 16, 2025 | Sep 30, 2033 | 2656 days remaining | Active |
| 26 | 26.28.59 | Mar 17, 2026 | Sep 30, 2026 | 99 days remaining | Warning |
What does Azul Zulu end of life mean for your organization?
When a version of Azul Zulu 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 Azul Zulu 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 Azul Zulu 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 →