Back to blog

OSSeva Blog

Operations

Patching the Whole Stack: Spring, Tomcat and Java 8 After EOL

6 min read

A Java 8 service built on Spring Boot 2.7 and Tomcat has four layers with four end dates, and no single open-source project patches all four: the JDK is maintained by its vendors to 2030, while Spring Boot 2.7, Spring Framework 5.3 and Tomcat 8.5 have already left support and Tomcat 9.0 leaves on 31 March 2027. Patching the stack means choosing a source for each layer. Dates were read on 17 November 2026 on the vendors' own pages. For the Spring layer, start with Spring Boot extended support.

Running Spring Framework in production? OSSeva patches and supports it, end-of-life versions included.

Spring Framework extended support: what is covered

What are the end dates for each layer of a Java 8 stack?

The JDK has the longest runway, to December 2030; every layer above it is already past or close to its open-source end.

LayerVersionOpen-source or vendor support endsSource
JDKJava 8Dec 2030 at Oracle (Extended), Temurin (at least), Corretto and AzulVendor roadmaps, read 17 Nov 2026
Servlet containerTomcat 8.5.xEnded 31 Mar 2024 (final 8.5.100)tomcat.apache.org whichversion
Servlet containerTomcat 9.0.x31 Mar 2027; 9.1.x releases continue to 31 Dec 2030tomcat.apache.org, announcement of 11 Feb 2026
FrameworkSpring Boot 2.7Ended 30 Jun 2023 (last 2.7.18)api.spring.io
FrameworkSpring Framework 5.3Ended 31 Aug 2024 (last 5.3.39)api.spring.io
SecuritySpring Security 5.7 and 5.8Ended 30 Jun 2023 and 31 Dec 2023api.spring.io

The JDK dates are on Java 8 end of life by distribution and the vendor comparison in which JDK vendor still patches Java 8, 11 and 17. Tomcat's dates are on Tomcat EOL dates.

Who covers which layer after end of life?

No route covers every layer without a gap, so write down which vendor owns each layer.

RouteJDKTomcatSpring Boot 2.7 and Framework 5.3
Broadcom Spring EnterpriseOpenJDK support listedTomcat coveredCommercial support to 30 Jun 2029
OpenLogic (Perforce)OpenJDK 8 and 11 to 30 Nov 2028Tomcat 8.5 to 31 Dec 2028Boot 2.7 and Framework 5.3 to 31 Oct 2027
HeroDevs NESNot on its Spring pageNot on its Spring pageBoot 2.7 and its managed Spring projects listed
OSSevaNot covered: the JDK vendors maintain itTomcat 8.5 to 11 covered, with patched builds for lines Apache no longer fixesBoot 2.7 and Framework 5.3 patched builds

Sources, read 17 November 2026: enterprise.spring.io (24x7 support for over 50 Spring projects plus OpenJDK and Tomcat) and api.spring.io for Broadcom; openlogic.com/products/long-term-support; herodevs.com/support/spring-nes; OSSeva's own pages. TuxCare's page returned an error on 17 November and is not in the table. A row says "not on its Spring page" where the page read lists nothing, which does not mean the vendor would refuse to quote it. Check each vendor for the layers you run.

Why is the JDK usually the layer you do not need to buy?

Because the free OpenJDK builds are maintained to December 2030 and the exposure is above them. Switching from Oracle JDK 8 to Temurin, Corretto or Azul is usually a runtime swap, and Corretto describes its builds as no-cost. Auditors ask which distribution you run, so record it. What then fails a scan is the Spring and Tomcat versions in the build. OSSeva does not patch the JDK; it patches the layers above it.

How do you patch Spring and Tomcat together?

Treat them as one change window, because Boot 2.7 embeds Tomcat 9.0 and the two move together. Spring Boot 2.7.18's requirements page lists Tomcat 9.0 as its embedded servlet container, so a Boot 2.7 service takes Tomcat 9.0 fixes through the Boot BOM, while a WAR deployed to a standalone Tomcat 8.5 or 9.0 gets them from Apache or a backport. Check which of the two your service uses.

  1. Record the JDK build, the Tomcat version, and the resolved Boot, Framework and Security versions per service.
  2. Move the JDK to a maintained build first; it needs no code change in most cases.
  3. Decide the Tomcat route before 31 March 2027, when Apache support for 9.0.x ends: move to 9.1.x, 10.1 or 11, or take backports.
  4. Decide the Spring route per service: upgrade to Boot 3.5 or 4.1, buy from Broadcom, or take backports while the move happens.

OSSeva delivers the Spring and Tomcat backports in one contract: Spring Boot extended support for Boot, Framework and Security, and Tomcat extended support for 8.5 to 11, with Critical CVEs patched within 48 hours and High within 7 days. Priced per application. See also the Tomcat 9 end of life checklist.

Frequently asked questions

Does anyone patch every layer of a Java 8 stack?

Broadcom's Spring Enterprise page lists Spring, OpenJDK and Tomcat, and OpenLogic's table lists OpenJDK 8, Tomcat 8.5 and Spring Boot 2.7. They differ in dates and in which Spring projects they cover, so compare per layer.

Is Tomcat 8.5 still supported?

Not by Apache. Tomcat 8.5.x support ended on 31 March 2024, and 8.5.100 was the final release. OpenLogic lists Tomcat 8.5 to 31 December 2028, and OSSeva ships patched 8.5 builds.

Which Tomcat does Spring Boot 2.7 use?

Tomcat 9.0, according to the Spring Boot 2.7.18 system requirements. Apache support for Tomcat 9.0.x ends on 31 March 2027.

Do I need to buy Java 8 support if I run Corretto or Temurin?

Not for the JDK itself: Corretto, Temurin, Azul and Oracle Extended Support all list December 2030. The unsupported layers are usually Spring and Tomcat.

Tags

Spring BootTomcatJava 8End of LifeExtended SupportPatching

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

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

Prefer to talk or read more first?

Book a call