EOL.Wiki EOL.Wiki
← ← Back to all products

Apache Tomcat

Active
Server Software Latest Version: 11.0.18 Latest Release: Jan 23, 2026

Apache Tomcat is an open-source Java Servlet container and web server for Java web applications.

Versions

9

Latest Version

11.0.18

Active Support

3

EOL

6

Lifecycle Timeline

Today
11.0
11.0
10.1
10.1
10.0
10.0
9.0
9.0
8.5
8.5
8.0
8.0
7
7
6
6
5
5
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
11.0Oct 3, 2024-No11.0.18No
Active
10.1Sep 23, 2022-No10.1.52No
Active
10.0Dec 3, 2020-Oct 31, 202210.0.27No
EOL
9.0Sep 27, 2017-Mar 31, 20279.0.115No
Active
8.5Mar 17, 2016-Mar 31, 20248.5.100No
EOL
8.0Jan 29, 2014-Jun 30, 20188.0.53No
EOL
7Jan 10, 2013-Mar 31, 20217.0.109No
EOL
6Oct 21, 2006-Dec 31, 20166.0.53No
EOL
5Sep 6, 2003-Sep 30, 20125.5.36No
EOL

Frequently Asked Questions

Which versions of Apache Tomcat have reached end of life?
The following Apache Tomcat versions have reached end of life and no longer receive security updates: 10.0, 8.5, 8.0, 7, 6, 5. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Tomcat 10.0?
Apache Tomcat 10.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache Tomcat?
The latest version of Apache Tomcat is 11.0.18, released in the 11.0 release cycle.
How many versions of Apache Tomcat are currently supported?
Apache Tomcat currently has 3 actively supported version(s): 11.0, 10.1, 9.0.
When does Apache Tomcat 11.0 reach end of life?
Apache Tomcat 11.0 does not have a specific end-of-life date announced yet.
What should I do when Apache Tomcat reaches end of life?
When a Apache Tomcat version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.