Complete end-of-life dates, support windows, and security status for all Eclipse Temurin versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 8 LTS | 8u492-b09 | Jul 29, 2021 | Dec 31, 2030 | 1697 days remaining | Active |
| 16 | 16.0.2+7 | Jul 30, 2021 | Sep 30, 2021 | 1682 days past EOL | EOL |
| 11 LTS | 11.0.31+11 | Aug 1, 2021 | Oct 31, 2027 | 540 days remaining | Active |
| 17 LTS | 17.0.19+10 | Sep 22, 2021 | Oct 31, 2027 | 540 days remaining | Active |
| 18 | 18.0.2.1+1 | Mar 24, 2022 | Sep 30, 2022 | 1317 days past EOL | EOL |
| 19 | 19.0.2+7 | Sep 26, 2022 | Mar 31, 2023 | 1135 days past EOL | EOL |
| 20 | 20.0.2+9 | Mar 23, 2023 | Sep 19, 2023 | 963 days past EOL | EOL |
| 21 LTS | 21.0.11+10 | Oct 10, 2023 | Dec 31, 2029 | 1332 days remaining | Active |
| 22 | 22.0.2+9 | Mar 20, 2024 | Sep 17, 2024 | 599 days past EOL | EOL |
| 23 | 23.0.2+7 | Sep 17, 2024 | Mar 18, 2025 | 417 days past EOL | EOL |
| 24 | 24.0.2+12 | Mar 20, 2025 | Sep 16, 2025 | 235 days past EOL | EOL |
| 25 LTS | 25.0.3+9 | Sep 22, 2025 | Sep 30, 2031 | 1970 days remaining | Active |
When a Eclipse Temurin 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 Eclipse Temurin 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 →