BlogTomcat

Tomcat end of life dates: 9.0, 9.1, 10.1 and 11

Scott Sternloff

By Scott Sternloff, Senior Enterprise Architect

LinkedIn · Updated · 8 min read

Tomcat end of life dates: 9.0, 9.1, 10.1 and 11
On this page

Apache Tomcat 9 reaches end of life on 31 March 2027, when support for the 9.0.x branch ends. A new 9.1.x branch will carry Tomcat 9 releases until 31 December 2030, but no 9.1.x release has been published yet. Tomcat 8.5 reached end of life on 31 March 2024, Tomcat 10.0 on 31 October 2022 and Tomcat 7 on 31 March 2021. Tomcat 10.1 and Tomcat 11.0 are supported, and no end of life date has been announced for either. Every date and latest Tomcat release below is from tomcat.apache.org, re-checked on 9 November 2026.

Apache Tomcat versions and end of life dates

Tomcat versionSpecificationMinimum JavaStatus and dateSpring Boot line that embeds itSource
11.0.xJakarta EE 11 (Servlet 6.1)17Supported, no EOL date announced. Latest 11.0.27 (12 Oct 2026)Boot 4.xWhich version
10.1.xJakarta EE 10 (Servlet 6.0)11Supported, no EOL date announced. Latest 10.1.61 (12 Oct 2026)Boot 3.xWhich version
9.0.xJava EE 8 (Servlet 4.0)8Support ends 31 March 2027. Latest 9.0.123 (12 Oct 2026)Boot 2.79.0 notice
9.1.xJava EE 8 (Tomcat 9 line)Not yet publishedNot released yet; planned releases until 31 December 2030n/a9.0 notice
10.0.xJakarta EE 9 (Servlet 5.0)8End of life 31 October 2022 (final 10.0.27)n/a10.0 notice
8.5.xServlet 3.17End of life 31 March 2024 (final 8.5.100)n/a8.5 notice
8.0.xServlet 3.17End of life 30 June 2018n/aWhich version
7.0.xServlet 3.06End of life 31 March 2021n/a7.0 notice

Sources: Which version do I want? and the Apache notices in the last column, read on 9 November 2026. Spring Boot lines follow the Spring Boot system requirements for 2.7, 3.5 and 4.0.

Keep Tomcat 9 supported past March 2027. Apache stops supporting Tomcat 9.0.x on 31 March 2027. AceMQ provides 24/7 Apache Tomcat support, with response targets from 15 minutes by plan, and plans the upgrade to 10.1 or 11 with you. See Tomcat support and patched builds.

Tomcat 9 end of life: what changes on 31 March 2027

The Apache Tomcat project announced the end of support for Tomcat 9.0.x on 11 February 2026. After 31 March 2027, new 9.0.x releases are highly unlikely, bug fixes for problems that affect only 9.0.x stop, and security vulnerability reports will not be checked against the 9.0.x branch, so security patches from the project stop too. Three months later (after 30 June 2027) the download links and documentation come down, although every release stays in the Apache archive.

Tomcat 9 gets a longer tail than earlier majors because it is the last major Tomcat version that implements Java EE rather than Jakarta EE. Instead of ending Tomcat 9 outright, the project will start a 9.1.x branch shortly before 9.0.x support ends. The differences are small but they matter for older configurations:

  • The APR/native connectors for HTTP, HTTPS and AJP are not available in 9.1.x.
  • Tomcat Native 2.0.x stays supported; Tomcat Native 1.3.x does not (it also ends on 31 March 2027, per tomcat.apache.org).
  • Teams on APR connectors should move to the NIO connectors now, and to NIO with JSSE or NIO with OpenSSL for HTTPS.

A server that does not use Tomcat Native, or already runs Tomcat Native 2.0.x, can treat 9.0.x to 9.1.x as a normal point release, so 9.1 is a drop-in path for it. The Tomcat team itself still recommends upgrading to a newer major version rather than settling on 9.1.

Tomcat 8.5 and Tomcat 10.0: already end of life

Tomcat 8.5 support ended on 31 March 2024. The last security fixes listed for it are in 8.5.99, and since then new vulnerability reports are not checked against 8.5 at all. That is the real cost of an EOL Tomcat: nobody tells you whether you are affected. In September 2026, for example, the project fixed CVE-2026-76183, an important-rated bypass of security constraints for WebSocket endpoints that affected every 9.0, 10.1 and 11.0 release up to 9.0.121, 10.1.59 and 11.0.25. Whether 8.5.x or 10.0.x is exposed has not been assessed by the project.

Tomcat 10.0 was a short-lived bridge to Jakarta EE and ended on 31 October 2022, with 10.0.27 as its final release. Anyone still on it should move to 10.1, which keeps the same jakarta.* packages.

Known exploitation is not hypothetical. CVE-2025-24813, a partial PUT flaw in the default servlet that can lead to remote code execution in some configurations, was made public on 10 March 2025, fixed in 9.0.99, 10.1.35 and 11.0.3, and added to CISA's Known Exploited Vulnerabilities catalog on 1 April 2025.

Upgrading Tomcat 9 to 10.1 or 11: the checklist

To upgrade Tomcat across major versions, the move from 9 to 10.1 is the hard one, because every javax.* servlet import becomes jakarta.*; 10.1 to 11 mostly raises the Java floor to 17 and removes SecurityManager support.

StepWhat breaksHow to handle it
1. Java versionTomcat 10.1 needs Java 11 and Tomcat 11.0 needs Java 17. Tomcat 9.0 runs on Java 8.Move the JDK first and test the application on it under Tomcat 9. Java LTS versions and end-of-life dates by vendor shows which JDK each vendor still patches.
2. javax to jakartaFrom Tomcat 10 the Servlet, JSP, EL and WebSocket APIs use jakarta.* packages, so applications must be recompiled.Run the Apache Tomcat Migration Tool for Jakarta EE ahead of time, or drop the application into webapps-javaee and let Tomcat convert it at deployment.
3. Libraries and frameworksAnything that still imports javax.servlet fails on Tomcat 10 and later. Spring Framework 6 and Spring Boot 3 need Jakarta.List the dependency tree and move each library to a Jakarta release. In Spring Boot the Boot version sets the Tomcat version.
4. APR/native to NIOThe APR connector was removed in 10.1.0-M5, and 9.1.x drops it.Switch to the NIO connectors while still on 9.0.x.
5. server.xml and context.xml defaultsSession persistence on restart is off by default from Tomcat 10, conf/web.xml defaults to UTF-8, and maxParameterCount is 1,000 from 9.0.74 and 10.1.8.Diff your files against the stock ones with the form in the 10.1 and 11.0 migration guides.
6. Test, then cut over side by sideStaging does not match production traffic.Run the new version beside the old one with its own $CATALINA_BASE, replay real requests, then switch the load balancer.

Old server.xml files carried forward between upgrades are where the surprises hide. Since 9.0.31, the release that fixed the Ghostcat AJP flaw CVE-2020-1938, the AJP connector listens on the loopback address and will not start without a secret unless secretRequired is set to false.

Embedded Tomcat: when Spring Boot reaches end of life, so does Tomcat

Many Tomcat installs are not installs at all. Spring Boot embeds Tomcat inside the application JAR: Spring Boot 2.7 uses Tomcat 9.0, Spring Boot 3.x uses Tomcat 10.1 and Spring Boot 4.x uses Tomcat 11.0. The last public Spring Boot 2.7 release, 2.7.18, manages Tomcat 9.0.83, so an application built on it without an override ships without the CVE-2025-24813 fix and every Tomcat 9 fix after it. Overriding the tomcat.version property works within a major line, but after 31 March 2027 there is no supported 9.0.x left to override to. See Spring Boot end of life dates for the framework dates.

Your options for an end-of-life Tomcat version

First, find every Tomcat you run. For standalone servers, bin/version.sh prints the exact version. For Spring Boot and other fat-JAR applications, look for tomcat-embed-core in the dependency tree or inside the JAR. For the other technologies AceMQ covers past end of life, see end-of-life software support.

  • Upgrade to Tomcat 10.1 or 11.0. The long-term answer, budgeted as a Jakarta migration plus a JDK upgrade. AceMQ's 24/7 Tomcat support includes the Java and Tomcat upgrade plan, led by named senior engineers.
  • Move to Tomcat 9.1. A reasonable bridge for Tomcat 9 servers that already use NIO connectors, with releases planned through 2030.
  • Stay on your version with support and patched builds. AceMQ's Tomcat support and patched builds cover versions Apache no longer patches, with response targets from 15 minutes by plan. For teams running Tomcat 9 after March 2027 on applications pinned to a Java EE stack or an old JDK, this keeps them running while the Jakarta migration is scheduled.
  • Use a commercial Spring subscription. Tanzu Spring includes Tomcat binaries alongside Spring and OpenJDK, and AceMQ brokers Tanzu Spring support.

Moving off WebLogic or JBoss to Tomcat? Start on 10.1 or 11.0, not a branch that is about to end.

Sources

Frequently Asked Questions

When is Tomcat 9 end of life?

Support for Apache Tomcat 9.0.x ends on 31 March 2027, as announced by the Tomcat team on 11 February 2026. A new 9.1.x branch will start shortly before that date and receive releases until 31 December 2030.

What is the Tomcat 9.1 release date?

Apache has not published an exact date. The Tomcat team announced on 11 February 2026 that releases from a new 9.1.x branch will be made available shortly before 9.0.x support ends on 31 March 2027, and that 9.1.x releases will continue until 31 December 2030. As of 9 November 2026 no 9.1.x release has been published.

What is Tomcat 9.1?

Tomcat 9.1.x is the continuation of Tomcat 9 after 9.0.x support ends. It keeps the Java EE 8 APIs but drops the APR/native connectors for HTTP, HTTPS and AJP, and supports only Tomcat Native 2.0.x. Servers that do not use Tomcat Native should be able to move to it like a point release.

Is Tomcat 8.5 end of life?

Yes. Apache Tomcat 8.5 reached end of life on 31 March 2024, and the final release was 8.5.100. New vulnerability reports are no longer checked against 8.5, so the project cannot tell you whether a new CVE affects it.

Is Tomcat 10 end of life?

Tomcat 10.0 reached end of life on 31 October 2022, with 10.0.27 as its final release. Tomcat 10.1 is supported and has no announced end of life date. Users of 10.0 should move to 10.1, which uses the same jakarta.* packages but requires Java 11.

Which Tomcat versions are currently supported?

As of 9 November 2026, Apache Tomcat 11.0, 10.1 and 9.0 are supported. Tomcat 9.0 support ends on 31 March 2027. No end of life date has been announced for 10.1 or 11.0.

When is Tomcat 11 end of life?

Apache has announced no end of life date for Tomcat 11.0 as of 9 November 2026. Tomcat 11.0 implements Jakarta EE 11 (Servlet 6.1) and needs Java 17 or later.

Which Java version does each Tomcat version need?

Tomcat 11.0 needs Java 17 or later, Tomcat 10.1 needs Java 11 or later, and Tomcat 9.0 and 10.0 run on Java 8 or later. Tomcat 8.5 required Java 7 or later.

Can I get security patches for Tomcat 8.5 or 9 after end of life?

Apache stops fixing Tomcat 9.0.x after 31 March 2027 and no longer checks vulnerability reports against 8.5.x. AceMQ's Tomcat support page covers the 24/7 support, emergency response, patched builds for versions Apache no longer fixes and upgrade planning that go with them.

Scott Sternloff

Author

Scott SternloffSenior Enterprise Architect

Senior Enterprise Architect at AceMQ. Writes the technical coverage here: RabbitMQ, Kafka and Redis architecture, clustering and migrations.

Talk to an engineer

Need a hand with Tomcat?

Senior engineers who run it in production. Get a quote or a free consultation, no sales pitch.

Free Consultation

Get Expert Eyes on Your Tomcat Environment

Whether you're troubleshooting a production incident, planning a migration, or want a second opinion on your architecture — our team is ready. No pitch, just answers.

Email Us