Azul Zulu 22 End of Life Date
Azul Zulu 22 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
Azul Zulu 22 was released on March 19, 2024 and support ended on September 17, 2024 — a supported lifespan of 6 months, in line with the 7 months median for Azul Zulu releases. It was not an LTS release; Azul Zulu reserves longer patch windows for its LTS versions. The last patch it will ever receive is 22.32.15, published July 16, 2024 — 2 months before support ended. It has been without security patches for 2 years. 4 newer Azul Zulu releases have shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 7 LTS | 7.56 | Jul 31, 2022 | EOL |
| 6 LTS | N/A | Dec 31, 2018 | EOL |
| 8 LTS | 8.96.0.205 | Dec 31, 2030 | Active |
| 9 (<abbr title='Short Term Support'>STS</abbr>) | 9.0.7.1 | Mar 31, 2018 | EOL |
| 10 (<abbr title='Short Term Support'>STS</abbr>) | 10.3.5 | Sep 30, 2018 | EOL |
| 11 LTS | 11.90.205 | Jan 31, 2032 | Active |
| 12 (<abbr title='Short Term Support'>STS</abbr>) | 12.3.11 | Sep 30, 2019 | EOL |
| 13 (<abbr title='Medium-Term Support'>MTS</abbr>) | 13.54.17 | Mar 31, 2023 | EOL |
What does Azul Zulu 22 end of life mean?
When Azul Zulu 22 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Azul Zulu 22 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Azul Zulu 27 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.