Oracle JDK 27 · Version Status

Oracle JDK 27 End of Life Date

Oracle JDK 27 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 27 is actively supported. EOL date: March 31, 2027.
📅 Get reminded before Oracle JDK 27 reaches EOL on March 31, 2027 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Mar 31, 2027
196 days remaining
Latest Release
27
Standard release
Release Date
Sep 15, 2026
Oracle JDK 27 series
Lifecycle detail

Oracle JDK 27 was released on September 15, 2026 and support is scheduled to end on March 31, 2027 — a planned supported lifespan of 7 months, in line with the 6 months median for Oracle JDK releases. It is not an LTS release; Oracle JDK reserves longer patch windows for its LTS versions. Its most recent patch is 27, published September 15, 2026.

← Oracle JDK 26 All Oracle JDK versions
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 →
All Oracle JDK Versions
VersionLatestEOL DateStatus
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 27 end of life mean?

When Oracle JDK 27 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Oracle JDK 27 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Oracle JDK 27 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Oracle JDK 27 reach end of life?
Oracle JDK 27 reached end of life on March 31, 2027. That is 196 days remaining.
Is Oracle JDK 27 still supported?
Yes, Oracle JDK 27 is currently supported. The EOL date is March 31, 2027.
What should I upgrade to from Oracle JDK 27?
The recommended upgrade from Oracle JDK 27 is Oracle JDK 27 — the latest actively supported version. Check the Oracle JDK full timeline for all supported versions.
What are the security risks of running Oracle JDK 27 past EOL?
When Oracle JDK 27 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Oracle JDK should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →