Java 17 end of life
Java 17 has no single end date; it depends on the vendor. Oracle lists Premier Support until September 2026 or later and Extended Support until September 2029 or later. Microsoft's earliest end of support is September 2027, Eclipse Temurin lists at least October 2027, Azul September 2029 and Amazon Corretto October 2029. OSSeva does not patch the JDK.
What now
Who provides Java 17 security patches once community support ends?
Your options, costed honestly- End of life
- Varies by vendor
- Released
- Sept 2021
- Final release
- Each vendor ships its own builds
- Successor
- Java 21 or Java 25 (both LTS)
Date published by Oracle Java SE support roadmap. We do not publish a lifecycle date we cannot source. Vendor dates read on each vendor's own page and checked against endoflife.date on 17 November 2026.
Last reviewed
Java versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Java 21 | 19 Sept 2023 | Varies by vendor | Supported |
| Java 17 (this page) | 14 Sept 2021 | Varies by vendor | Supported |
| Java 11 | 25 Sept 2018 | Varies by vendor | Supported |
| Java 8 | 18 Mar 2014 | January 2019 (Oracle public updates for commercial use) | End of life |
| Java LTS | 18 Mar 2014 | Varies by version and vendor | Supported |
End-of-life dates are published by each project and checked against endoflife.date.
What stops, and when, depending on your Java 17 vendor
- Oracle Premier Support for Java 17 is listed until September 2026, marked "or later" on Oracle's page. Extended Support runs to September 2029 or later, and a footnote on the page says the Extended Support fee is waived from October 2026 to September 2029 for Java SE 17.
- Oracle JDK 17 updates were under a permissive licence until September 2024. Releases from 15 October 2024 are under the Java SE OTN licence, and Oracle tells users who want a permissive licence to move to Oracle JDK 25 or later.
- On the free OpenJDK builds the end dates differ by vendor: Microsoft's earliest end of support is September 2027, Temurin lists at least October 2027, Azul September 2029 and Corretto October 2029. Red Hat's full support ends 31 December 2027, followed by a paid ELS-1 phase to 31 January 2029.
- What stops being covered sooner is the ecosystem around a Java 17 estate: Spring Boot 3.4 and 3.5 are already past open-source support, and Tomcat 9.0.x loses Apache support on 31 March 2027.
What actually breaks in the upgrade
Which vendor you run decides your date
Java 17 from Oracle, Temurin, Corretto, Azul, Red Hat and Microsoft are builds of the same OpenJDK 17 code, each with its own end date. Moving between them is usually a runtime swap, not a code change, so the first question is which build is in your containers and on your hosts, not which number.
Java 17 is the floor for Spring Boot 3 and 4
Spring Boot 3.4, 3.5, 4.0 and 4.1 all require at least Java 17, and Tomcat 11 requires 17 as well. A service already on Java 17 has done the hard part of the Boot 3 move; what remains is the javax to jakarta rename and Spring Security 6. Spring Boot 2 to 3 migration guide.
Java 17 to 21 or 25 is the easier hop
Both are LTS releases. Spring Boot 3.4 and later run on Java 21, and Boot 3.5 runs up to Java 25. Most of the breakage in older estates came earlier, at Java 8 to 17, from removed JDK modules and encapsulated internals, so a Java 17 service usually moves with a smaller change set. Java 21 end of life.
Java 17 end of life dates by vendor
Oracle's Extended Support and Azul's roadmap run to September 2029, Amazon Corretto lists October 2029 and Eclipse Temurin lists at least October 2027. Each cell is the vendor's own date.
Java 17 support end by vendor, each date read on the vendor's own page on 17 November 2026
| Vendor | What the date is | Date |
|---|---|---|
| Oracle (Java SE) | Premier Support / Extended Support | Sep 2026 / Sep 2029 (both marked "or later") |
| Eclipse Temurin | End of Availability | At least Oct 2027 |
| Amazon Corretto | End of life | Oct 2029 |
| Azul Zulu | End of Production Support (add 2 years for Extended Support) | Sep 2029 |
| Red Hat build of OpenJDK | End of full support / end of paid ELS-1 | 31 Dec 2027 / 31 Jan 2029 |
| Microsoft Build of OpenJDK | Earliest end of support (initial target) | Sep 2027 |
Sources, all read 17 November 2026: oracle.com Java SE support roadmap (page dated 20 October 2026); adoptium.net/support; aws.amazon.com/corretto/faqs; azul.com/products/azul-support-roadmap; access.redhat.com/articles/1299013 (page updated 13 August 2026); learn.microsoft.com/java/openjdk/support (page updated 4 August 2026, "initial targets"). Cross-checked on endoflife.date.
Which Spring Boot and Tomcat lines need Java 17
Spring Boot 3.4, 3.5, 4.0 and 4.1 need at least Java 17, and so does Tomcat 11.0. Spring Boot 2.7 and Tomcat 9.0 run on Java 17 but do not require it.
Minimum and maximum Java by framework line, read 17 November 2026
| Framework line | Java it runs on | Open-source support | Source |
|---|---|---|---|
| Spring Boot 2.7.18 | 8 to 21 | Ended 30 Jun 2023 | docs.spring.io Boot 2.7.18 |
| Spring Boot 3.4.13 | 17 to 24 | Ended 31 Dec 2025 | docs.spring.io Boot 3.4.13 |
| Spring Boot 3.5.16 | 17 to 25 | Ended 30 Jun 2026 | docs.spring.io Boot 3.5.16 |
| Spring Boot 4.0.9 | 17 to 27 | Ends 31 Dec 2026 | docs.spring.io Boot 4.0.9 |
| Spring Boot 4.1.2 | 17 to 27 | Ends 31 Jul 2027 | docs.spring.io Boot 4.1.2 |
| Tomcat 9.0.x | 8 and later | Apache support ends 31 Mar 2027 | tomcat.apache.org whichversion and 9.0.x announcement |
| Tomcat 10.1.x | 11 and later | Supported | tomcat.apache.org whichversion |
| Tomcat 11.0.x | 17 and later | Supported | tomcat.apache.org whichversion |
What OSSeva covers on top of Java 17
OSSeva does not patch the JDK. On top of Java 17 it covers Spring Framework, Spring Boot and Spring Security lines that have left open-source support, such as Boot 3.4 and 3.5 and the Boot 2.x line that still runs on Java 17, and Apache Tomcat 9 once Apache support ends on 31 March 2027. Fixes ship as signed builds through your repository manager: Critical CVEs within 48 hours and High within 7 days on the Patch tier.
Which of the two you need depends on what sits on the JDK. List the Spring Boot and Tomcat versions you run and the support options are on the two pages below.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Stay on a maintained OpenJDK 17 build | Run Temurin, Corretto, Azul Zulu, a Red Hat build or a Microsoft build and track that vendor's end date. | Hours to days | Free on the vendors' no-cost builds; check each vendor's terms | Start here. It answers the runtime question before anything paid, and Corretto and Azul list the longest dates for 17. |
| Move to Java 21 or Java 25 | Newer LTS releases with later end dates from every vendor in the table. | Weeks, driven by libraries and the frameworks on top | Engineering time | The durable fix. Check the framework line first: Boot 3.4 runs to Java 24, Boot 3.5 to Java 25. |
| Oracle Extended Support or Red Hat ELS-1 | Oracle lists Extended Support to September 2029 or later; Red Hat sells an optional ELS-1 phase to 31 January 2029. | Procurement | Vendor terms; not covered here | Compare against a free maintained build first. Ask each vendor what is included. |
| Keep Spring and Tomcat patched | Third-party patched builds for the framework and server layers that end before the JDK does. | Days to onboard | Subscription | This is the gap OSSeva fills: Spring and Tomcat, not the JVM. |
What OSSeva does for Java 17
Not covered — and here is why
OSSeva does not patch the Java runtime and will not quote for it; the vendors in the table maintain it. What OSSeva covers on top of Java 17 is the stack that runs on it: Spring Framework, Spring Boot and Spring Security after open-source support, and Apache Tomcat 9 after 31 March 2027. Critical CVEs are patched within 48 hours and High within 7 days.
Spring Framework extended supportWhat your auditor will say
Requirement 6.3.3 asks for security patches on in-scope components. A JDK build still receiving vendor updates meets it for the runtime; the finding then moves up to the framework and server layer.
Auditors ask which distribution, not which version. Record the vendor, the build and its end date in your asset inventory.
When does Java 17 reach end of life?
There is no single date. Oracle lists Premier Support until September 2026 or later and Extended Support until September 2029 or later. Microsoft's earliest end of support is September 2027, Eclipse Temurin lists at least October 2027, Azul September 2029 and Amazon Corretto October 2029. Read each vendor's page on 17 November 2026.
Is Java 17 still supported in 2026?
Yes, by every vendor in the table. Java 17 is an LTS release and each vendor still ships quarterly updates. What differs is how long each will keep doing it, and whether the support is free or paid.
Which JDK vendor supports Java 17 the longest?
Of the free builds, Amazon Corretto lists the latest date, October 2029, followed by Azul and Oracle's Extended Support at September 2029. Eclipse Temurin lists at least October 2027 and Microsoft September 2027 as an initial target. Dates can be extended, so check the vendor page when you plan.
Does Spring Boot 3 need Java 17?
Yes. Spring Boot 3.4, 3.5, 4.0 and 4.1 all require at least Java 17, according to the Spring Boot system requirements pages. Spring Boot 2.7.18 runs on Java 8 to 21.
Does OSSeva patch Java 17?
No. OSSeva patches Spring and Tomcat running on Java, not the Java runtime. The JDK vendors in the table maintain it.
Get a quote
Still running Java 17?
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.
Prefer to talk or read more first?