EOL.WikiEOL.Wiki
← ← Back to all products

Oracle JDKEnd of Life (EOL) Dates & Support Status

Active
Runtimes & JDKsLatest Version: 27Latest Release: Sep 15, 2026

Oracle JDK is Oracle's commercial Java Development Kit with long-term support for enterprise applications.

Support summary

Oracle JDK 17 reaches EOL in 3 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Sep 30, 2026

Oracle JDK 17 · 3 days left

Supported cycles

4

6 lts

Versions

28

Latest Version

27

Active Support

4

EOL

24

Lifecycle Timeline

Mar 22, 2022As of Sep 27, 2026
27Active · Mar 31, 2027
26EOL · Sep 18, 2026
25Active · Sep 30, 2030
24EOL · Sep 16, 2025
23EOL · Mar 18, 2025
22EOL · Sep 17, 2024
21Active · Sep 30, 2028
20EOL · Sep 19, 2023
19EOL · Mar 21, 2023
18EOL · Sep 20, 2022
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
27Sep 15, 2026MaintainedMar 31, 202727No
Active
26Mar 17, 2026EndedSep 18, 202626.0.2.1No
EOL
25Sep 16, 2025MaintainedSep 30, 203025.0.4.1
Yes
Active
24Mar 18, 2025EndedSep 16, 202524.0.2No
EOL
23Sep 17, 2024EndedMar 18, 202523.0.2No
EOL
22Mar 19, 2024EndedSep 17, 202422.0.2No
EOL
21Sep 19, 2023MaintainedSep 30, 202821.0.12.1
Yes
Active
20Mar 21, 2023EndedSep 19, 202320.0.2No
EOL
19Sep 20, 2022EndedMar 21, 202319.0.2No
EOL
18Mar 22, 2022EndedSep 20, 202218.0.2.1No
EOL
17Sep 14, 2021MaintainedSep 30, 202617.0.20.1
Yes
Active
16Mar 16, 2021EndedSep 14, 202116.0.2No
EOL
15Sep 15, 2020EndedMar 16, 202115.0.2No
EOL
14Mar 17, 2020EndedSep 16, 202014.0.2No
EOL
13Sep 17, 2019EndedMar 17, 202013.0.2No
EOL
12Mar 19, 2019EndedSep 17, 201912.0.2No
EOL
11Sep 25, 2018EndedSep 30, 202311.0.32.1
Yes
EOL
10Mar 20, 2018EndedSep 25, 201810.0.2No
EOL
9Sep 21, 2017EndedMar 20, 20189.0.4No
EOL
8Mar 18, 2014EndedMar 31, 20228u503
Yes
EOL
7Jul 11, 2011EndedJul 31, 20197u351
Yes
EOL
6Dec 12, 2006EndedDec 31, 20186u211No
EOL
5Sep 30, 2004EndedOct 30, 20095.0u85No
EOL
1.4Feb 13, 2002EndedOct 30, 20081.4.2_42No
EOL
1.3May 8, 2000EndedMar 31, 20061.3.1_32No
EOL
1.2Dec 4, 1998EndedNov 30, 20031.2.2_18No
EOL
1.1Feb 18, 1997EndedOct 9, 20021.1.8_010No
EOL
1.0Jan 23, 1996EndedMay 7, 19961.0.2No
EOL

Data sources

Embed this badge

Oracle JDK end-of-life support status badge

Show Oracle JDK's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Oracle JDK end-of-life status](https://eol.wiki/badge/oracle-jdk.svg)](https://eol.wiki/oracle-jdk/)

HTML

<a href="https://eol.wiki/oracle-jdk/"><img src="https://eol.wiki/badge/oracle-jdk.svg" alt="Oracle JDK end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of Oracle JDK have reached end of life?
The following Oracle JDK versions have reached end of life and no longer receive security updates: 26, 24, 23, 22, 20, 19, 18, 16 (and 16 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Oracle JDK 26?
Oracle JDK 26 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Oracle JDK?
The latest version of Oracle JDK is 27, released in the 27 release cycle.
How many versions of Oracle JDK are currently supported?
Oracle JDK currently has 4 actively supported version(s): 27, 25, 21, 17.
When does Oracle JDK 27 reach end of life?
Oracle JDK 27 is scheduled to reach end of life on Mar 31, 2027.
What should I do when Oracle JDK reaches end of life?
When a Oracle JDK version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.