Oracle JDK 26 · Version Status
Oracle JDK 26 End of Life Date
Oracle JDK 26 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.
⚠
Oracle JDK 26 is past end of life. This version no longer receives security patches. EOL since September 2026 — migrate to a supported version immediately.
EOL Date
Sep 2026
EOL since September 2026
Latest Release
26.0.2.1
Standard release
Release Date
Mar 17, 2026
Oracle JDK 26 series
Where these dates come from
End of lifeSep 2026Vendor's own page (our correction) · oracle.com · checked Nov 8, 2026medium · 1 source agrees ReleaseMar 17, 2026Vendor's own page, read by our adapter · oracle.com · checked Nov 3, 2026high · 3 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Oracle JDK 26 was released on March 17, 2026 and support ended in September 2026 — a supported lifespan of 7 months, in line with the 6 months median for Oracle JDK releases. It was not an LTS release; Oracle JDK reserves longer patch windows for its LTS releases. Its latest release on record is 26.0.2.1, published August 18, 2026 — before support ended. It has been past its end-of-life date for 40 days.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 → ·
View score card →
Extended Support
Extended Oracle JDK 26 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.2 |
May 7, 1996 |
EOL |
| 1.1 |
1.1.8_010 |
Oct 9, 2002 |
EOL |
| 1.2 |
1.2.2_18 |
Nov 30, 2003 |
EOL |
| 1.3 |
1.3.1_32 |
Mar 31, 2006 |
EOL |
| 1.4 |
1.4.2_42 |
Oct 30, 2008 |
EOL |
| 5 |
5.0u85 |
Oct 30, 2009 |
EOL |
| 6 |
6u211 |
Dec 31, 2018 |
EOL |
| 7 LTS |
7u351 |
Jul 31, 2019 |
EOL |
What does Oracle JDK 26 end of life mean?
When Oracle JDK 26 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 Oracle JDK 26 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Oracle JDK 25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Oracle JDK 26 reach end of life?
Oracle JDK 26 reached end of life in September 2026. This version is no longer receiving security patches.
Is Oracle JDK 26 still supported?
No. Oracle JDK 26 reached end of life in September 2026 and is no longer receiving security patches.
What should I upgrade to from Oracle JDK 26?
The recommended upgrade from Oracle JDK 26 is
Oracle JDK 25 — the latest actively supported version. Check the
Oracle JDK full timeline for all supported versions.
What are the security risks of running Oracle JDK 26 past EOL?
Since Oracle JDK 26 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Oracle JDK should migrate immediately or implement compensating controls.