Azul Zulu End of Life Dates

other

Developers rely on Azul Zulu for its ability to provide high-quality, open-source Java Development Kits and Java Runtimes, which has been a crucial tool since its creation. The product is maintained by Azul Systems, a company known for its expertise in Java and other programming languages, ensuring that Azul Zulu stays up-to-date with the latest developments in the Java ecosystem. By tracking end-of-life dates and supported versions, developers can plan their upgrades and migrations in advance, minimizing potential disruptions to their applications and ensuring a smooth transition to newer versions.

The end-of-life landscape for Azul Zulu is complex, with a total of 21 versions, out of which 15 have already reached their end-of-life, leaving 6 active versions that are still supported. The latest stable version, 11.86.21, is the current benchmark for developers, while version 26 is next in line to expire on 2026-09-30. This information is crucial for developers to plan their upgrades and migrations, as failing to do so may leave their applications vulnerable to potential security risks. The most recent end-of-life date was 2025-09-16 for version 24, marking the end of support for that particular release.

With no recorded Common Vulnerabilities and Exposures (CVEs) and zero critical CVEs, Azul Zulu presents a clean security slate. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status is applicable. Given this secure posture, developers should continue to monitor the end-of-life timelines and plan their upgrades to ensure they stay within the supported versions, taking advantage of the latest security patches and features that come with each new release, ultimately maintaining the integrity and security of their applications.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
27 Sep 15, 2026—Mar 31, 2027in 159d27.28.101—Active
26 Mar 17, 2026—Sep 30, 202623d ago26.32.203—EOL
25 LTSSep 16, 2025—Sep 30, 2033in 2534d25.36.205—Active
24 Mar 18, 2025—Sep 16, 2025402d ago24.32.13—EOL
23 Sep 17, 2024—Mar 18, 2025584d ago23.32.11—EOL
22 Mar 19, 2024—Sep 17, 2024766d ago22.32.15—EOL
21 LTSSep 19, 2023—Sep 30, 2031in 1803d21.52.203—Active
20 Mar 21, 2023—Sep 19, 20231130d ago20.32.11—EOL
19 Sep 20, 2022—Mar 31, 20231302d ago19.32.13—EOL
18 Mar 12, 2022—Sep 30, 20221484d ago18.32.13—EOL
17 LTSSep 15, 2021—Sep 30, 2029in 1073d17.68.203—Active
16 Mar 16, 2021—Sep 30, 20211849d ago16.32.15—EOL
15 Sep 15, 2020—Mar 31, 20231302d ago15.46.17—EOL
14 Mar 17, 2020—Sep 30, 20202214d ago14.29.23—EOL
13 Sep 17, 2019—Mar 31, 20231302d ago13.54.17—EOL
12 Mar 19, 2019—Sep 30, 20192580d ago12.3.11—EOL
11 LTSSep 25, 2018—Jan 31, 2032in 1926d11.90.205—Active
10 Mar 27, 2018—Sep 30, 20182945d ago10.3.5—EOL
9 Sep 21, 2017—Mar 31, 20183128d ago9.0.7.1—EOL
8 LTSApr 8, 2014—Dec 31, 2030in 1530d8.96.0.205—Active
6 LTSJan 21, 2014—Dec 31, 20182853d agoN/A—EOL
7 LTSSep 25, 2013—Jul 31, 20221545d ago7.56—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions