Oracle JDK · Lifecycle Status

Oracle JDK End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Oracle JDK versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Oracle JDK 26 reaches end of life on September 18, 2026. Plan your migration now — 40 days remaining.
Running an EOL version? Get matched with support options — free ↓
📅 Get reminded before Oracle JDK 26 reaches EOL on September 18, 2026 — alerts 90, 30 & 7 days out.
Google →
Latest Active
25.0.4
25 series
Next EOL
26
Sep 18, 2026
Active Versions
2
of 27 total
EOL Versions
23
no longer patched
40 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 199619971998199920002001200220032004200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920301.01.11.21.31.4567891011121314151617181920212223242526TODAY
23 versions of Oracle JDK are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
1.0 1.0.2 Jan 23, 1996 May 7, 1996 11051 days past EOL EOL
1.1 1.1.8_010 Feb 18, 1997 Oct 9, 2002 8705 days past EOL EOL
1.2 1.2.2_18 Dec 4, 1998 Nov 30, 2003 8288 days past EOL EOL
1.3 1.3.1_32 May 8, 2000 Mar 31, 2006 7436 days past EOL EOL
1.4 1.4.2_42 Feb 13, 2002 Oct 30, 2008 6492 days past EOL EOL
5 5.0u85 Sep 30, 2004 Oct 30, 2009 6127 days past EOL EOL
6 6u211 Dec 12, 2006 Dec 31, 2018 2778 days past EOL EOL
7 LTS 7u351 Jul 11, 2011 Jul 31, 2019 Jul 19, 2022
Oracle Java SE Subscription (ended)
2566 days past EOL EOL
8 LTS 8u501 Mar 18, 2014 Mar 31, 2022 Dec 31, 2030
Oracle Java SE Subscription
1592 days past EOL EOL
9 9.0.4 Sep 21, 2017 Mar 20, 2018 3064 days past EOL EOL
10 10.0.2 Mar 20, 2018 Sep 25, 2018 2875 days past EOL EOL
11 LTS 11.0.32 Sep 25, 2018 Sep 30, 2023 Jan 31, 2032
Oracle Java SE Subscription
1044 days past EOL EOL
12 12.0.2 Mar 19, 2019 Sep 17, 2019 2518 days past EOL EOL
13 13.0.2 Sep 17, 2019 Mar 17, 2020 2336 days past EOL EOL
14 14.0.2 Mar 17, 2020 Sep 16, 2020 2153 days past EOL EOL
15 15.0.2 Sep 15, 2020 Mar 16, 2021 1972 days past EOL EOL
16 16.0.2 Mar 16, 2021 Sep 14, 2021 1790 days past EOL EOL
17 LTS 17.0.20 Sep 14, 2021 Sep 30, 2026 Sep 30, 2029
Oracle Java SE Subscription
52 days remaining Warning
18 18.0.2.1 Mar 22, 2022 Sep 20, 2022 1419 days past EOL EOL
19 19.0.2 Sep 20, 2022 Mar 21, 2023 1237 days past EOL EOL
20 20.0.2 Mar 21, 2023 Sep 19, 2023 1055 days past EOL EOL
21 LTS 21.0.12 Sep 19, 2023 Sep 30, 2028 Sep 30, 2031
Oracle Java SE Subscription
783 days remaining Active
22 22.0.2 Mar 19, 2024 Sep 17, 2024 691 days past EOL EOL
23 23.0.2 Sep 17, 2024 Mar 18, 2025 509 days past EOL EOL
24 24.0.2 Mar 18, 2025 Sep 16, 2025 327 days past EOL EOL
25 LTS 25.0.4 Sep 16, 2025 Sep 30, 2030 Sep 30, 2033
Oracle Java SE Subscription
1513 days remaining Active
26 26.0.2 Mar 17, 2026 Sep 18, 2026 40 days remaining Warning
EOL date vs extended support. The EOL Date column is the end of standard, included support. Oracle Java SE Subscription is a paid programme. Versions past their EOL date are only receiving patches if you hold that subscription — without it, they are unpatched. 2 versions of Oracle JDK are past the standard EOL date but still inside the extended support window.
Oracle JDK EOL status badge Live EOL badge for your README — updates automatically at every build. [![Oracle JDK EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Foracle-jdk.json)](https://endoflife.ai/oracle-jdk)

What does Oracle JDK end of life mean for your organization?

When a version of Oracle JDK 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 Oracle JDK 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.

Your options when Oracle JDK reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Oracle JDK versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Oracle JDK Support Options

Oracle JDK has 23 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Oracle JDK exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Oracle JDK?
The next Oracle JDK version reaching EOL is 26 on September 18, 2026. See the full table above for all version EOL dates.
When is the Oracle JDK support end date?
The next Oracle JDK support end date is September 18, 2026, when version 26 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Oracle JDK?
The latest active version of Oracle JDK is 25.0.4. Always verify against the table above as support windows can change.
What happens when Oracle JDK reaches end of life?
When Oracle JDK reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Oracle JDK?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Oracle JDK versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

✓ Cross-checked against official Oracle lifecycle documentation (2026-07-17) · Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →
Oracle JDK end-of-life status badge