Supported

Apache Tomcat 10.1 end of life

Apache Tomcat 10.1 is supported and has no announced end-of-life date. The project's version page lists 10.1.x as a supported line, and 10.1.61, announced on 12 October 2026, is the latest release. Tomcat sets an end date for each branch by public notice, as it did when 10.0 ended on 31 October 2022, and no such notice exists for 10.1.

What now

Who provides Apache Tomcat 10.1 security patches once community support ends?

Tomcat 9 Extended Support and Security Patching
End of life
No date announced
Released
Sept 2022
Final release
10.1.62 (latest, announced 16 November 2026)
Successor
Tomcat 11.0

Date published by Apache Tomcat: which version do I want?. We do not publish a lifecycle date we cannot source.

Last reviewed

Apache Tomcat versions: release and end-of-life dates

Apache Tomcat release and end-of-life dates
VersionReleasedEnd of lifeStatus
Apache Tomcat 10.1 (this page)26 Sept 2022No date announcedSupported
Apache Tomcat 10.08 Dec 202031 October 2022End of life
Apache Tomcat 9.027 Sept 201731 March 2027Approaching
Apache Tomcat 8.517 Mar 201631 March 2024End of life
Apache Tomcat 729 Jun 201031 March 2021End of life

End-of-life dates are published by each project and checked against endoflife.date.

What will stop when end of life is announced

  • Nothing has stopped. 10.1 receives regular releases, and Spring Boot 3 applications embed it: Boot 3.4.13 manages Tomcat 10.1.50.
  • When a date is set, the 10.0 notice shows what follows. Releases from the branch become highly unlikely, bugs that affect only that branch are not fixed, and security reports are no longer checked against it. Three months later, the download and documentation links come down.
  • No notice period is promised. The version page commits to at least 12 months' notice before 9.1.x ends, and makes no equivalent statement for 10.1.

What actually breaks in the upgrade

How Tomcat retires a branch

Tomcat publishes no fixed lifetime per version. The version page refers to the 10 years for which major versions are typically supported, but the real date arrives as a notice. 10.0 shows how quickly that can happen once a successor exists: it ended on 31 October 2022, five weeks after 10.1.0 became the first stable Jakarta EE 10 release.

11.0 needs Java 17

Tomcat 11.0 implements the Jakarta EE 11 specifications, including Servlet 6.1, and needs Java 17 or later. 10.1 runs on Java 11 and later. Both use the jakarta namespace, so the move from 10.1 does not repeat the javax to jakarta change.

Embedded Tomcat moves with Spring Boot

Spring Boot 3.4 manages Tomcat 10.1 and Spring Boot 4.1 manages Tomcat 11.0, so for most Spring applications the Tomcat upgrade arrives with the Boot upgrade. Until then, a Boot 3 application can set tomcat.version to the latest 10.1 release without waiting for a new Boot release.

Your options, costed honestly

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

OptionWhat it isEffortCostOur view
Stay on 10.1 and take each releaseApache still fixes 10.1, so the work is keeping up with releases.Hours per releaseEngineering timeThe right answer today, as long as releases are applied.
Upgrade to Tomcat 11.0Jakarta EE 11 and a Java 17 baseline.Days to weeks, mostly the Java versionEngineering timeWorth planning now if the JVM is already on 17 or later.
OSSeva support for Tomcat 10.1Connector and hardening reviews, CVE notifications, and operations.DaysSubscriptionOne supplier for the container and the rest of the stack.

What OSSeva does for Apache Tomcat 10.1

OSSeva supports this line

Tomcat 10.1 is in OSSeva's Tomcat versions table as a current line, and the Patch tier covers Tomcat 10.x. While Apache supports 10.1, fixes come from Apache's own releases. Assure adds the connector configuration audit, a hardening review and the Tomcat 10 to 11 migration assessment; Operate adds 24/7 JVM and Tomcat monitoring and runs major version migrations.

Need 24/7 Tomcat support while you upgrade? AceMQ, our sister company, provides it.

Apache Tomcat extended support

What your auditor will say

PCI DSS v4 Requirement 6.3.3

Every system component in the cardholder data environment needs its applicable security patches. A component with no upstream fix supply needs a patched source or a documented compensating control.

SOC 2 CC7.1

Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.

Compliance library Apache Tomcat end of life dates for every version

Questions

Apache Tomcat 10.1: common questions

Book a 15-minute call

What is the Tomcat 10.1 end of life date?

None has been announced. As of October 2026, the Tomcat version page lists 10.1.x as supported, and the project has published no end-of-life notice for it.

Is Tomcat 10.1 still supported?

Yes. The latest release is 10.1.62, announced on 16 November 2026.

How much notice will Apache give before Tomcat 10.1 ends?

The project has not said. It promises at least 12 months' notice for the end of 9.1.x and makes no statement about 10.1. When 10.0 ended, the notice gave the end date and removed downloads three months later.

What should I upgrade Tomcat 10.1 to?

Tomcat 11.0, which implements Jakarta EE 11 and needs Java 17 or later. There is no namespace change between 10.1 and 11.0.

Which Java version does Tomcat 10.1 need?

Java 11 or later, according to the Tomcat version page.

Get a quote

Still running Apache Tomcat 10.1?

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