Back to blog

OSSeva Blog

Operations

Tomcat 9 end of life checklist: what to do before 31 March 2027

6 min read

The short answer

Apache's Tomcat version page says end of support for Tomcat 9.0.x is expected no earlier than 31 March 2027 (checked 14 November 2026). Before then: list every server on 9.0, choose 9.1, 10.1 or 11 for each application, and test the javax-to-jakarta change for any application that moves to 10.1 or later. Applications that cannot move in time need patched 9.0 builds.

Nothing is switched off on the day: Tomcat 9 keeps serving requests. What ends is Apache's supply of fixes for the 9.0 line, and with it the security advisories that vulnerability scanners match against. The latest 9.0 release on Apache's download page is 9.0.124. The Tomcat 9 end of life dates page holds the reference dates; this checklist is the planning side.

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

Apache Tomcat extended support: what is covered

When does each Tomcat line end?

LineStatus on 14 Nov 2026End of supportMinimum Java
Tomcat 7.0Archived31 Mar 20216
Tomcat 8.5Archived31 Mar 20247
Tomcat 9.0Supported (9.0.124)Expected no earlier than 31 Mar 20278
Tomcat 9.1Planned: starts when 9.0 reaches end of supportNot determined; at least 12 months' noticeNot stated
Tomcat 10.1SupportedNo date announced11
Tomcat 11.0Supported (11.0.29)No date announced17

Sources: tomcat.apache.org/whichversion.html, read 14 November 2026, and endoflife.date/tomcat for 7.0, 8.5 and 9.0. Java levels by vendor are on Java LTS end of life dates.

Tomcat 9 end of life checklist: 10 steps

  1. Inventory every Tomcat server. Record the Tomcat version, the Java version, the connectors in use and the applications deployed. $CATALINA_HOME/bin/version.sh prints the server version. Why: you cannot plan a date you have not mapped to machines.
  2. Scan application code and dependencies for javax.* imports. grep -rl "import javax\.servlet" src/ is a start; also check third-party jars. Why: this is the work that decides whether 10.1 or 11 is realistic.
  3. Choose a target per application: 9.1, 10.1 or 11. Use the decision table below. Why: one answer for the whole estate is rarely right.
  4. Trial the Apache Tomcat Migration Tool for Jakarta EE on one application. It converts javax.* to jakarta.* (tomcat.apache.org/download-migration.cgi). Why: it either works cleanly or shows you the blocker while there is time.
  5. Line up the Java upgrade the target needs. 10.1 needs Java 11 or later and 11.0 needs Java 17 or later. Why: the JDK move is a second change that has to be scheduled too.
  6. Book test and cutover windows before March. Why: change freezes and quarter-end releases eat the calendar.
  7. List the applications that cannot move by 31 March 2027. Write down the owner, the reason and the target date. Why: these are the ones that need cover.
  8. Check what your auditors expect. See PCI DSS Requirement 6.3.3 and end-of-life software. Why: Tomcat is often the internet-facing tier, so scanner findings land here first.
  9. Watch Tomcat CVEs. Tomcat CVEs and the versions that fix them lists what was fixed where. Why: an end date is only as costly as the vulnerabilities published after it.
  10. Set a go or no-go date. For example the end of January, with a budget decision for anything still on 9.0. Why: it forces the straggler list to become a plan.

Tomcat 9 vs 10.1 vs 11: which should you run?

Move to 10.1 or 11 if your applications can take the jakarta namespace change; stay on the 9 line only to buy time. Tomcat 10 and later implement Jakarta EE, so every servlet, filter, listener and JSP import moves from javax.* to jakarta.*. The step-by-step version is in Tomcat 9 to 10.1 migration steps and the javax to jakarta migration guide.

SituationTargetEffortRisk
You can rebuild the application and have Java 17Tomcat 11.0Jakarta move plus Java 17Lowest long term: newest line, no end date announced
You can rebuild it but are on Java 11Tomcat 10.1Jakarta moveA later move to 11 needs Java 17
Third-party WARs you cannot rebuild10.1 or 11 through the migration toolTest each WARSome WARs will not convert; find out early
You must stay on javax.* but want Apache fixesTomcat 9.1.x, when the branch startsSmall, but check connectorsAPR/Native connector is not available in 9.1.x; end date not determined
Cannot move by 31 March 2027Stay on 9.0 with patched buildsNo code changeYou depend on a third party for fixes

What the 9.1 branch changes in practice is covered in Tomcat 9.1 and the end of 9.0.

What if you cannot move by 31 March 2027?

Keep 9.0 patched after end of support. OSSeva Patch ships Critical (CVSS 9.0+) fixes within 48 hours and High within 7 days, priced per application server. OSSeva covers Tomcat 9.0 today and backports fixes to 9.0 after Apache stops, as signed builds delivered through your own repository manager. Tomcat 9 extended support after 31 March 2027 lists what is covered. A senior engineer replies within 1 business day with a quote.

One honest limit: if every application can move to 10.1 or 11 this quarter, do that and skip the cover. Cover is for the applications that cannot.

Frequently asked questions

When does Tomcat 9 support end?

Apache's version page says end of support for 9.0.x is expected no earlier than 31 March 2027, as read on 14 November 2026.

What is Tomcat 9.1?

A planned branch that Apache says will start when 9.0.x reaches end of support. It keeps the Java EE namespace, drops the APR/Native connector, and has no end date yet: Apache promises at least 12 months' notice.

Can I keep running Tomcat 9 after March 2027?

Yes, it keeps running. Fixes then come from the 9.1.x branch once it starts, or from a third-party patched 9.0 build. Unpatched, an internet-facing Tomcat collects scanner findings.

Tags

Apache TomcatTomcat 9End of LifeChecklistJakarta 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