Back to blog

OSSeva Blog

Operations

Tomcat 9.1: Release Date, and When Tomcat 9.0 Ends (31 March 2027)

Matt ReynoldsUpdated 5 min read

Running Tomcat 8.5 or a pinned 9.0.x build? The community will not patch it for you. See who provides patched Tomcat builds after end of life, or check the Tomcat 9 end-of-life dates.

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

Apache Tomcat extended support: what is covered

Tomcat 9.1 release date and Tomcat 9 end of life

There is no Tomcat 9.1 release yet. Apache will start the 9.1.x branch shortly before Tomcat 9.0.x support ends on 31 March 2027, and 9.1.x releases will continue until 31 December 2030. Tomcat 9.1 is not a new major version. It is the 9.0 line continued, without the APR/native connectors.

Key dates

EventDate
Tomcat 9.0.x end of support31 March 2027
First Tomcat 9.1.x releaseShortly before 31 March 2027 (no exact date announced)
Tomcat Native 1.3.x end of support31 March 2027
9.0.x download links and docs removed from tomcat.apache.orgAfter 30 June 2027 (archive copies stay available)
Tomcat 9.1.x releases continue until31 December 2030

Source: Apache's end of support announcement for Tomcat 9.0.x (11 February 2026), checked 22 October 2026. The project's Which Version Do I Want? page is more cautious: it says 9.0 support ends "no earlier than" 31 March 2027 and that no end date has been set for 9.1.x, with at least 12 months notice promised.

For most users the move from 9.0.x to 9.1.x will be a normal point release upgrade. The exception is anyone using the APR/native connectors. They are not available in 9.1.x, so those users have configuration work to do first.

Why Tomcat 9 gets extended support

Tomcat 9 is the last major Tomcat version that supports Java EE. Tomcat 10 and later implement Jakarta EE, where the APIs moved from javax.* to jakarta.*. Because many applications cannot make that change quickly, the Tomcat community decided to support Tomcat 9 beyond the ten years major versions usually get.

Tomcat 9.0 is on the 2027 open-source end-of-life calendar, listed by quarter with the other lines ending that year. Moving to 10.1 instead? Tomcat 10.1 end of life has its dates. Planning the move? The Tomcat 9 end of life checklist turns it into 10 steps. New to the term? What EOL means for Tomcat 9 and every other software line is explained on one page.

VersionPlatformMin JavaStatus
Tomcat 11.0.xJakarta EE 1117Supported
Tomcat 10.1.xJakarta EE 1011Supported
Tomcat 9.0.xJava EE 88End of support 31 Mar 2027
Tomcat 8.5.xJava EE 77EOL 31 Mar 2024

What is Tomcat 9.1.x, and what changes from 9.0.x

  • The APR/native connectors for HTTP, HTTPS and AJP are removed. Move to the NIO HTTP and NIO AJP connectors, and for TLS to NIO+JSSE or NIO+OpenSSL.
  • Tomcat Native 1.3.x is not supported. NIO+OpenSSL continues through Tomcat Native 2.0.x.
  • Security fixes, bug fixes and features continue to be back-ported as they were for 9.0.x.

Which Tomcat 9.0.x release fixes which CVEs?

Apache lists 58 CVEs fixed across the ten 9.0.x releases from 9.0.113 to 9.0.123. Each CVE is fixed in the release shown, so running 9.0.123 or later clears all of them. The CVE IDs shown are the ones Apache rates Important; the Apache page has the full list and the affected-version range for each.

Fixed inAnnouncedCVEs fixedSeverity (Apache rating)Important CVEs
9.0.12312 Oct 202672 important, 5 lowCVE-2026-101356, CVE-2026-101296
9.0.12215 Sep 2026124 important, 3 moderate, 5 lowCVE-2026-86350, CVE-2026-78383, CVE-2026-77791, CVE-2026-76183
9.0.12118 Aug 2026114 important, 1 moderate, 6 lowCVE-2026-68763, CVE-2026-68569, CVE-2026-65927, CVE-2026-65182
9.0.1207 Jul 202622 low—
9.0.11923 Jun 202661 moderate, 5 low—
9.0.11810 May 202672 moderate, 5 low—
9.0.1173 Apr 202641 important, 1 moderate, 2 lowCVE-2026-34486
9.0.11620 Mar 202661 important, 2 moderate, 3 lowCVE-2026-29146
9.0.11523 Jan 202611 moderate—
9.0.1137 Dec 202521 moderate, 1 low—

Source: Apache Tomcat 9.x vulnerabilities, checked 22 October 2026. Releases with no listed CVE (such as 9.0.114) and releases before 9.0.113 are not in the table. If your build is pinned to an older 9.0.x release or you are on 8.5, none of these fixes reach you from the community. See Tomcat extended support for patched builds of those lines.

What happens after 31 March 2027

After 31 March 2027 9.0.x releases are highly unlikely beyond the final one made shortly before that date, and the project no longer checks security reports against the 9.0.x branch. Fixes continue on the 9.1.x branch instead.

Upgrade or stay on 9.1.x?

The Tomcat project itself encourages Tomcat 9 users to upgrade rather than settle on 9.1.x, using the Tomcat Migration Tool for Jakarta EE. If your application and its libraries can move to jakarta, target Tomcat 10.1 or 11. If they cannot, 9.1.x buys time until the end of 2030. Keep patching either way: CVE-2025-24813, a path equivalence flaw in the default servlet fixed in 9.0.99, 10.1.35 and 11.0.3, has been on CISA's Known Exploited Vulnerabilities catalogue since 1 April 2025.

Estates still on Tomcat 8.5, or on vendor builds pinned to old 9.0.x releases, get neither path. OSSeva backports Tomcat security fixes to those versions; see Apache Tomcat support, the Tomcat 9 and Tomcat 8.5 end-of-life pages, and Tomcat CVEs in enterprise Java.

Frequently asked questions

When is the Tomcat 9.1 release date?

Apache has not set an exact date. The 9.1.x branch starts shortly before 9.0.x support ends on 31 March 2027. No 9.1 release exists today.

How long will Tomcat 9 be supported?

The 9.0.x branch until 31 March 2027, and the 9.1.x branch until 31 December 2030.

What is the difference between Tomcat 9 and 10?

Tomcat 9 implements Java EE 8 with javax.* packages. Tomcat 10 and later implement Jakarta EE with jakarta.* packages, so applications must be migrated, as covered in our javax to jakarta migration guide.

What is the latest Tomcat 9 version?

9.0.123, according to tomcat.apache.org on 22 October 2026.

Tags

Apache TomcatTomcat 9End of LifeJakarta EEJava

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