Tomcat 9 EOL: support for 9.0.x ends 31 March 2027
Tomcat 9 EOL is 31 March 2027: the Apache Tomcat team announced on 11 February 2026 that support for the 9.0.x branch ends on that date. Shortly before then, releases move to a new 9.1.x branch that continues until 31 December 2030 but drops the APR/native connectors. Tomcat 10 and later use the jakarta namespace, which is the migration most estates are avoiding.
What now
Which vendors provide Apache Tomcat 9.0 security patches after 31 March 2027?
Tomcat 9 Extended Support and Security Patching- End of life
- 31 March 2027
- Released
- Sept 2017
- Final release
- 9.0.124 (current)
- Successor
- Tomcat 10.1 or Tomcat 11.0
Date published by Apache Tomcat team, End of support for Apache Tomcat 9.0.x (11 February 2026). We do not publish a lifecycle date we cannot source. Dates checked on tomcat.apache.org and endoflife.date on 17 November 2026.
Last reviewed
Apache Tomcat versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Apache Tomcat 10.1 | 26 Sept 2022 | No date announced | Supported |
| Apache Tomcat 10.0 | 8 Dec 2020 | 31 October 2022 | End of life |
| Apache Tomcat 9.0 (this page) | 27 Sept 2017 | 31 March 2027 | Approaching |
| Apache Tomcat 8.5 | 17 Mar 2016 | 31 March 2024 | End of life |
| Apache Tomcat 7 | 29 Jun 2010 | 31 March 2021 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 March 2027
- Security and bug-fix releases on the 9.0.x line. Apache says releases after 31 March 2027 are highly unlikely, with the final 9.0.x release expected shortly before the date.
- Security checks on 9.0.x. After the date Apache will not check security vulnerability reports against the 9.0.x branch, so advisories stop saying whether 9.0 is affected, and that is what most vulnerability scanners key on.
- Downloads and documentation. After 30 June 2027 Apache removes the 9.0.x download links and documentation links from tomcat.apache.org; every 9.0.x release stays in the Apache archive.
- Nothing else. Tomcat 9 keeps serving requests; what ends is the fix supply.
What actually breaks in the upgrade
9 to 10.1 is the javax to jakarta rename, and it touches every file
Tomcat 10 onwards implements Jakarta EE, which moved every servlet API package from javax.* to jakarta.*. This is not a configuration change: every import in every servlet, filter, listener and JSP has to move, and every dependency that touches the servlet API has to be on a Jakarta-compatible version. The Tomcat project ships a migration tool that rewrites bytecode at deploy time, which is a genuine bridge, but running production on bytecode rewriting indefinitely is not a strategy.
The migration tool is a real option for buying time
Apache's migration tool for Jakarta EE can convert a javax-based WAR to jakarta at build time or on deployment. For estates with third-party WARs they cannot rebuild, this is often the only viable path, and it is worth prototyping early because it either works cleanly or reveals a blocker immediately.
The planning window is already short
The date is known and public, and it is now a matter of months. The difference between planning the Jakarta migration this quarter and discovering it in early 2027 is the difference between a scheduled project and an emergency one, because the javax to jakarta move is not a task that can be compressed.
What are the Tomcat 9 end of life dates for 9.0, 9.1 and Tomcat Native?
Tomcat 9.0.x support ends on 31 March 2027, the 9.1.x branch is announced to run to 31 December 2030, and Tomcat Native 1.3.x ends on the same day as 9.0.x. Apache's announcement and its Which Version page word the dates differently, so both are shown.
Tomcat 9 dates from Apache, read 17 November 2026
| Item | Date | Where Apache says it |
|---|---|---|
| Tomcat 9.0.x end of support | 31 March 2027 | End of support announcement, 11 February 2026. The Which Version page says expected no earlier than that date. |
| Final 9.0.x release | Shortly before 31 March 2027 | End of support announcement |
| 9.0.x downloads and docs links removed | After 30 June 2027 | End of support announcement; releases stay in the archive |
| Tomcat Native 1.3.x end of support | 31 March 2027 | End of support announcement |
| Tomcat 9.1.x releases | Start shortly before 31 March 2027, continue to 31 December 2030 | Announcement. The Which Version page says no 9.1.x end date has been determined and promises at least 12 months' notice. |
| Tomcat 10.1 and 11.0 | No end date announced | Which Version page |
Sources: tomcat.apache.org/tomcat-9.0.x-eos.html and tomcat.apache.org/whichversion.html, both read on 17 November 2026; endoflife.date/tomcat agrees on 31 March 2027 for 9.0. The latest 9.0.x release is 9.0.124.
How many Apache Tomcat 9 vulnerabilities were fixed in 2025 and 2026?
Apache's security page lists 58 advisory entries for Tomcat 9.0.x releases from 9.0.113 on 7 December 2025 to 9.0.123 on 12 October 2026: 12 rated Important, 12 Moderate and 34 Low, none Critical. A Tomcat 9.0 server on any older release is missing the fixes below, and after 31 March 2027 Apache will stop checking new reports against the 9.0.x branch.
Advisory entries fixed per Tomcat 9.0.x release, as counted on tomcat.apache.org/security-9.html on 17 November 2026
| Fixed in | Release date | Entries | Important | Moderate | Low |
|---|---|---|---|---|---|
| 9.0.123 | 12 October 2026 | 7 | 2 | 0 | 5 |
| 9.0.122 | 15 September 2026 | 12 | 4 | 3 | 5 |
| 9.0.121 | 18 August 2026 | 11 | 4 | 1 | 6 |
| 9.0.120 | 7 July 2026 | 2 | 0 | 0 | 2 |
| 9.0.119 | 23 June 2026 | 6 | 0 | 1 | 5 |
| 9.0.118 | 10 May 2026 | 7 | 0 | 2 | 5 |
| 9.0.117 | 3 April 2026 | 4 | 1 | 1 | 2 |
| 9.0.116 | 20 March 2026 | 6 | 1 | 2 | 3 |
| 9.0.115 | 23 January 2026 | 1 | 0 | 1 | 0 |
| 9.0.113 | 7 December 2025 | 2 | 0 | 1 | 1 |
| Total | 58 | 12 | 12 | 34 |
Severity is Apache's own rating. Releases with no entry (such as 9.0.114 and the latest, 9.0.124) are not listed. The per-CVE detail, with affected ranges, is on the Tomcat CVE guide.
What happens to a Tomcat 9 server after the end of life date?
It keeps running, and it stops getting 9.0.x fixes. The server needs one of three things: a move to 9.1.x (a point release unless it uses the APR/native connectors), a move to 10.1 or 11 (the jakarta change), or a patched 9.0 build from a provider that backports Apache's fixes. OSSeva ships those patched 9.0 builds from 31 March 2027, with Critical CVEs within 48 hours and High within 7 days.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Migrate to Tomcat 10.1 or 11 | The javax to jakarta namespace migration, across every servlet-touching dependency. | Weeks to months depending on third-party WARs | Engineering time | The right answer, and the one that needs the most lead time. Start before 2027. |
| Use the Jakarta migration tool | Rewrite javax to jakarta at build or deploy time. | Days to prototype | Engineering time | A genuine bridge, especially for third-party WARs you cannot rebuild. Prove it early. |
| Extended support on Tomcat 9 | Backported CVE fixes on the 9.0 line past March 2027. | Days to onboard | Subscription | Right when the Jakarta migration is a real project that will not finish by the date. |
| Stay on 9 unpatched after the date | No upstream 9.0.x fixes from April 2027; fixes continue only on the 9.1.x branch. | None | Zero now | Tomcat is usually the internet-facing edge of a Java estate, which makes this the worst place to carry unpatched CVEs. |
What OSSeva does for Apache Tomcat 9.0
OSSeva patches this line
OSSeva backports CVE fixes to Tomcat 8.5 and covers 9.0 today: until 31 March 2027 the 9.0 fixes come from Apache's own releases, and from that date OSSeva backports them to 9.0, delivered as signed builds through your repository manager. Tomcat sits at the edge of most Java estates, so we treat its CVEs as priority backports rather than batching them.
Need 24/7 Tomcat support while you upgrade? AceMQ, our sister company, provides it.
Apache Tomcat extended supportWhat your auditor will say
Tomcat is frequently in the cardholder data environment as the application tier. Requirement 6.3.3 applies directly, and an edge component with unpatched CVEs is the least defensible position in an assessment.
CC7.1. Tomcat CVEs are well publicised and reliably picked up by scanners, so an unpatched instance shows up in evidence whether or not you flag it.
When is Tomcat 9 EOL?
Support for Apache Tomcat 9.0.x ends on 31 March 2027, per the Apache Tomcat team's announcement of 11 February 2026. Releases then continue on the 9.1.x branch until 31 December 2030, and the 9.0.x download links are removed after 30 June 2027.
How many vulnerabilities has Tomcat 9 had recently?
Apache's Tomcat 9 security page lists 58 advisory entries fixed across ten 9.0.x releases from 9.0.113 (7 December 2025) to 9.0.123 (12 October 2026): 12 rated Important, 12 Moderate and 34 Low, none Critical. Counted on 17 November 2026; the latest release, 9.0.124, has no entry.
What is Tomcat 9.1?
The Apache Tomcat branch that continues the 9.x line after 9.0.x support ends, with releases until 31 December 2030. It keeps the javax namespace but removes the APR/native connectors for HTTP, HTTPS and AJP, so deployments that rely on Tomcat Native need to move to the NIO connectors first.
Is Tomcat 9 still supported?
Yes. 9.0.x is supported until 31 March 2027, and the 9.1.x branch continues until 31 December 2030. Tomcat 8.5 is the line that is already end of life, having reached it on 31 March 2024. Apache's Which Version page words the 9.0.x date as expected no earlier than 31 March 2027 and says no end date has been determined for 9.1.x, with at least 12 months' notice.
What is the difference between Tomcat 9 and Tomcat 10?
Tomcat 10 implements Jakarta EE, which renamed every servlet API package from javax.* to jakarta.*. This is the single breaking change and it affects every servlet, filter, listener and JSP, plus every dependency that touches the servlet API.
How do I migrate from Tomcat 9 to Tomcat 10?
Either update every javax.* servlet import to jakarta.* and move all servlet-touching dependencies to Jakarta-compatible versions, or use the Apache migration tool for Jakarta EE to rewrite the bytecode at build or deploy time. Prototype the tool early: for third-party WARs you cannot rebuild it is often the only path.
Can I get security patches for Tomcat 9 after March 2027?
From Apache, only on the 9.1.x branch, which continues the javax-based 9.x line until 31 December 2030 but drops the APR/native connectors. For 9.0.x itself, third-party extended support providers including OSSeva backport CVE fixes to end-of-life Tomcat lines: 8.5 now, and 9.0 once Apache's support ends on 31 March 2027.
Is Tomcat 8.5 still supported?
No. Tomcat 8.5 reached end of life on 31 March 2024 and the project publishes no further releases on that line.
Get a quote
Still running Apache Tomcat 9.0?
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.
Prefer to talk or read more first?