Supported

Java LTS end of life

Java has no single end-of-life date. Each LTS version (8, 11, 17, 21 and 25) gets its own end date from each vendor that builds it, and Oracle, Eclipse Temurin, Amazon Corretto, Azul, Red Hat and Microsoft publish different dates. Oracle's roadmap, updated 20 October 2026, shows Java 17 Premier Support ending in September 2026 and Extended Support in September 2029. The date that matters is your vendor's.

What now

Who provides Java LTS security patches once community support ends?

Your options, costed honestly
End of life
Varies by version and vendor
Released
Mar 2014
Final release
Each vendor ships its own builds
Successor
Java 25 (LTS)

Date published by Oracle Java SE support roadmap. We do not publish a lifecycle date we cannot source. Dates checked on each vendor's lifecycle page on 14 November 2026.

Last reviewed

What will stop when end of life is announced

  • Nothing stops on one date. Each vendor ends updates per version on its own schedule, and the table below lists them side by side.
  • Oracle's roadmap shows Java 17 moving from Premier to Extended Support in September 2026. Premier Support for 21 ends in September 2028 and for 25 in September 2030, and Oracle marks the later dates for 17 and above as "or later".
  • Between LTS versions, releases get about six months of updates: Eclipse Temurin's table shows Java 27, released in September 2026, ending in March 2027.
  • What erodes around an older Java is the ecosystem: Spring Boot 3 and 4 need Java 17, and Tomcat 11 needs Java 17.

What actually breaks in the upgrade

Which Java versions are LTS?

Oracle's roadmap and endoflife.date list 8, 11, 17, 21 and 25 as long-term support releases. Java 25 reached general availability on 16 September 2025. Oracle lists Java 29 as the next planned LTS, in September 2027.

Which Java version does your framework need?

Spring Boot 2.7 runs on Java 8 and later, and Spring Boot 3.5 and 4.0 need Java 17. Tomcat 9.0 needs Java 8, Tomcat 10.1 needs Java 11 and Tomcat 11.0 needs Java 17. The framework line you are on often sets the lowest Java you can run, so check both dates before you choose a JDK. Spring Boot end of life dates.

A vendor change is usually the cheap fix

Moving between OpenJDK distributions is usually a runtime swap rather than a code change, and every vendor in the table publishes its own end date. Record the distribution in your asset inventory, not just the number.

OSSeva does not patch the Java runtime

The JVM is maintained by the OpenJDK vendors in the table. OSSeva patches the layer above it: Spring Framework, Spring Boot, Spring Security and Tomcat. Java 8 end of life by distribution.

Java LTS end dates by vendor

Each cell is the vendor's own date, read on 14 November 2026. Oracle shows Premier and Extended Support; Red Hat shows end of full support and the end of its paid ELS-1 phase. Microsoft does not build Java 8.

VersionOracle (Premier / Extended)Eclipse TemurinAmazon CorrettoAzulRed Hat (full / ELS-1)Microsoft
Java 8Mar 2022 / Dec 2030At least Dec 2030Dec 2030Dec 203030 Nov 2026 / 31 Dec 2032Not built
Java 11Sep 2023 / Jan 2032At least Oct 2027Jan 2032Jan 203231 Oct 2024 / 31 Jan 2032Sep 2027
Java 17Sep 2026 / Sep 2029At least Oct 2027Oct 2029Sep 202931 Dec 2027 / 31 Jan 2029Sep 2027
Java 21Sep 2028 / Sep 2031At least Dec 2029Oct 2030Sep 203131 Dec 2029 / 30 Sep 2031Sep 2028
Java 25Sep 2030 / Sep 2033At least Sep 2031Oct 2032Sep 203331 Dec 2030 / 30 Sep 2033Sep 2030

Sources: oracle.com Java SE support roadmap (page dated 20 October 2026; 17 and later marked "or later"); adoptium.net/support ("End of Availability"); aws.amazon.com/corretto/faqs (end of life); azul.com support roadmap (production support); access.redhat.com/articles/1299013 (the Java 8 full-support date carries an asterisk on Red Hat's page); learn.microsoft.com/java/openjdk/support (earliest end of support, described as initial targets). Cross-checked against endoflife.date/oracle-jdk.

Which Java version does each framework need?

The minimum Java level for the Spring and Tomcat lines OSSeva's customers run most, from each project's own page on 14 November 2026.

Framework lineMinimum JavaSource
Spring Boot 2.78docs.spring.io Spring Boot 2.7 requirements
Spring Boot 3.517docs.spring.io Spring Boot 3.5 system requirements
Spring Boot 4.017docs.spring.io Spring Boot 4.0 system requirements
Tomcat 9.08tomcat.apache.org/whichversion.html
Tomcat 10.111tomcat.apache.org/whichversion.html
Tomcat 11.017tomcat.apache.org/whichversion.html

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Use a maintained OpenJDK buildChoose Temurin, Corretto, Zulu, Red Hat or Microsoft builds and track that vendor's end date.Hours to daysFree for the builds with a free tier; check each vendorStart here. It answers the runtime question before anything paid.
Move to a newer LTSJava 17, 21 or 25, depending on the frameworks you run.Weeks to months, driven by frameworksEngineering timeThe durable fix. The framework move usually decides the schedule.
A vendor's paid extended support for the JDKOracle, Red Hat (ELS) and Azul each sell support beyond the free dates in the table.ProcurementPer vendor; not covered hereCompare against a free maintained build first. Ask each vendor what is included.
Keep Spring and Tomcat patchedThird-party patched builds for the framework and server layer that end earlier than the JDK.Days to onboardSubscriptionThis is the gap OSSeva fills: Spring and Tomcat, not the JVM.

What OSSeva does for Java LTS

Not covered — and here is why

OSSeva does not patch the Java runtime and will not quote for it. The OpenJDK vendors in the table maintain it. What OSSeva covers is the stack on top: Spring Framework, Spring Boot, Spring Security and Apache Tomcat.

Spring Framework extended support

What your auditor will say

PCI DSS 4.0

Requirement 6.3.3 asks for security patches on in-scope components. A Java build still receiving vendor updates meets it for the runtime; the finding then moves up to the framework.

SOC 2

Auditors ask which distribution, not which version. Record the vendor and its end date in your inventory.

Compliance library Spring Framework end of life dates for every version

Questions

Java LTS: common questions

Book a 15-minute call

Is Java 11 still supported?

It depends on your vendor. Oracle lists Premier Support for Java 11 as ended in September 2023 and Extended Support to January 2032, Amazon Corretto lists January 2032, and Eclipse Temurin lists at least October 2027. See the table, read 14 November 2026.

When does Java 17 reach end of life?

There is no single date. Oracle lists Premier Support ending in September 2026 and Extended Support in September 2029; Temurin lists at least October 2027; Corretto lists October 2029; Microsoft lists September 2027 as an initial target.

Is Java 8 end of life?

Not for every vendor: Oracle Extended Support, Corretto and Azul list December 2030, and Red Hat's extended phase runs to December 2032. The Java 8 end of life page covers the distributions in detail.

Does OSSeva patch Java?

No. OSSeva patches Spring and Tomcat running on Java, not the Java runtime.

Get a quote

Still running Java LTS?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call