Eclipse Temurin 27 · Version Status

Eclipse Temurin 27 End of Life Date

Eclipse Temurin 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.

⚡ Eclipse Temurin 27 reaches end of life on March 23, 2027. Plan your migration now — 174 days remaining.
📅 Get reminded before Eclipse Temurin 27 reaches EOL on March 23, 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 23, 2027
174 days remaining
Latest Release
jdk-27+35
Standard release
Release Date
Sep 22, 2026
Eclipse Temurin 27 series
Lifecycle detail

Eclipse Temurin 27 was released on September 22, 2026 and support is scheduled to end on March 23, 2027 — a planned supported lifespan of 6 months, in line with the 6 months median for Eclipse Temurin releases. It is not an LTS release; Eclipse Temurin reserves longer patch windows for its LTS versions. Its most recent patch is jdk-27+35, published September 22, 2026.

← Eclipse Temurin 26 All Eclipse Temurin versions
18 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
8/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 →  ·  View score card →
Recommended upgrade path
Eclipse Temurin 25
Latest release: 25.0.4.1+1 · EOL: Sep 30, 2031
View full Eclipse Temurin timeline →
Extended Support
Extended Eclipse Temurin 27 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Eclipse Temurin Versions
VersionLatestEOL DateStatus
8 LTS 8u504-b01 Dec 31, 2030 Active
16 16.0.2+7 Sep 30, 2021 EOL
11 LTS 11.0.32.1+1 Oct 31, 2027 Active
17 LTS 17.0.20.1+1 Oct 31, 2027 Active
18 18.0.2.1+1 Sep 30, 2022 EOL
19 19.0.2+7 Mar 31, 2023 EOL
20 20.0.2+9 Sep 19, 2023 EOL
21 LTS 21.0.12.1+1 Dec 31, 2029 Active

What does Eclipse Temurin 27 end of life mean?

When Eclipse Temurin 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: 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 Eclipse Temurin 27 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Eclipse Temurin 25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Eclipse Temurin 27 reach end of life?
Eclipse Temurin 27 reached end of life on March 23, 2027. That is 174 days remaining.
Is Eclipse Temurin 27 still supported?
Eclipse Temurin 27 is still supported but approaching end of life on March 23, 2027. Begin planning your migration now.
What should I upgrade to from Eclipse Temurin 27?
The recommended upgrade from Eclipse Temurin 27 is Eclipse Temurin 25 — the latest actively supported version. Check the Eclipse Temurin full timeline for all supported versions.
What are the security risks of running Eclipse Temurin 27 past EOL?
When Eclipse Temurin 27 reaches end of life, the maintainers stop issuing 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 Eclipse Temurin should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →