OpenJDK builds from Oracle End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all OpenJDK builds from Oracle versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9 | 9.0.4 | Sep 21, 2017 | Mar 20, 2018 | 3017 days past EOL | EOL |
| 10 | 10.0.2 | Mar 20, 2018 | Sep 25, 2018 | 2828 days past EOL | EOL |
| 11 | 11.0.2 | Sep 25, 2018 | Mar 19, 2019 | 2653 days past EOL | EOL |
| 12 | 12.0.2 | Mar 19, 2019 | Sep 17, 2019 | 2471 days past EOL | EOL |
| 13 | 13.0.2 | Sep 17, 2019 | Mar 17, 2020 | 2289 days past EOL | EOL |
| 14 | 14.0.2 | Mar 17, 2020 | Sep 16, 2020 | 2106 days past EOL | EOL |
| 15 | 15.0.2 | Sep 15, 2020 | Mar 16, 2021 | 1925 days past EOL | EOL |
| 16 | 16.0.2 | Mar 16, 2021 | Sep 14, 2021 | 1743 days past EOL | EOL |
| 17 | 17.0.2 | Sep 14, 2021 | Mar 22, 2022 | 1554 days past EOL | EOL |
| 18 | 18.0.2.1 | Mar 22, 2022 | Sep 20, 2022 | 1372 days past EOL | EOL |
| 19 | 19.0.2 | Sep 20, 2022 | Mar 21, 2023 | 1190 days past EOL | EOL |
| 20 | 20.0.2 | Mar 21, 2023 | Sep 19, 2023 | 1008 days past EOL | EOL |
| 21 | 21.0.2 | Sep 19, 2023 | Mar 19, 2024 | 826 days past EOL | EOL |
| 22 | 22.0.2 | Mar 19, 2024 | Sep 17, 2024 | 644 days past EOL | EOL |
| 23 | 23.0.2 | Sep 17, 2024 | Mar 18, 2025 | 462 days past EOL | EOL |
| 24 | 24 | Mar 18, 2025 | Sep 16, 2025 | 280 days past EOL | EOL |
| 25 | 25 | Sep 16, 2025 | Mar 17, 2026 | 98 days past EOL | EOL |
| 26 | 26 | Mar 17, 2026 | Sep 18, 2026 | 87 days remaining | Warning |
What does OpenJDK builds from Oracle end of life mean for your organization?
When a version of OpenJDK builds from Oracle 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 OpenJDK builds from Oracle 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 OpenJDK builds from Oracle 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 →