OSSeva Blog
OperationsTomcat extended support: 10 questions to ask before you sign
What to ask before you buy Tomcat extended support
Ask ten things: which Tomcat lines are covered, how fast fixes arrive, what you receive, what an auditor gets, what sits outside the contract, and what happens when you leave. Put each answer in the contract, not the sales deck. The table gives the question, what a usable answer looks like, and OSSeva's answer from what it publishes. Tomcat extended support from OSSeva covers Tomcat 8.5, 9.0, 10.0, 10.1 and 11; the same ten questions work on any provider.
The date that makes this urgent is public: Apache ends support for Tomcat 9.0.x on 31 March 2027 (Tomcat 9 EOL). Servers that can take Apache's 9.1.x branch need no contract at all, so question 7 comes first in practice.
Running Apache Tomcat in production? OSSeva patches and supports it, end-of-life versions included.
Apache Tomcat extended support: what is coveredThe 10 questions, with what a good answer looks like
| # | Question | A usable answer | OSSeva's answer |
|---|---|---|---|
| 1 | Which Tomcat lines and builds are covered? | Whole lines, listed by version, with dates. A list of named builds means your build must be one of them. | Lines 8.5, 9.0, 10.0, 10.1 and 11. 8.5 and 10.0 get patched builds now; 9.0 gets them after 31 March 2027. |
| 2 | How fast do fixes arrive, and when does the clock start? | A number of hours or days per severity, written into the contract, with the start event named. | Critical CVEs within 48 hours, High within 7 days. Ask for the start event in writing from every provider. |
| 3 | What exactly do I receive? | A signed build, the format, and how it reaches your repository manager. | Signed builds (GPG for packages, cosign for container images, with SHA-256 checksums) as Docker images, apt and yum packages or zip archives. Patches apply to upstream source, with no fork. |
| 4 | What evidence will my auditor get? | A record per release, not a letter that says "patched". | A CVE record per release (CVE id, CVSS, affected versions, delivery date, build identifier), an attestation letter, an SBOM and a VEX statement per CVE. |
| 5 | Does it cover the JDK under Tomcat? | A plain yes or no. | No. OSSeva does not patch the JDK. Tomcat 8.5 and 9.0 on Java 8 are covered as Tomcat; the JDK comes from your Java vendor (see Java LTS end of life dates). |
| 6 | Does it cover Tomcat embedded in an application? | Which embedded forms count, and which do not. | Tomcat embedded in a Spring Boot application OSSeva covers is included in that Spring Boot coverage. Tomcat sealed inside a vendor appliance is the vendor's to patch (see finding embedded Tomcat). |
| 7 | What if I can move to Apache's 9.1.x branch instead? | The provider tells you when you do not need to buy. | Apache's 9.1.x is a point-release move unless you use the APR/native connectors. OSSeva's offer is for servers that cannot take it, and for 9.0 builds after 31 March 2027. |
| 8 | What is the price unit? | A unit you can count: servers, instances or cores, and what happens when you add one. | Priced per application server. Figures are given on request, not published. |
| 9 | Who answers when something breaks, and how fast? | Response times by priority, in writing. | On the Operate tier: P1 in 15 minutes, P2 in 1 hour, P3 in 4 hours, with 24/7 JVM and Tomcat monitoring. |
| 10 | What happens when I leave? | Whether the builds keep running, and whether moving to a newer Tomcat is an ordinary upgrade. | Builds are upstream Tomcat with security fixes backported, so a later move to 10.1 or 11 is the same upgrade you would do anyway, with the jakarta work still to plan (Tomcat 9 to 10.1 migration). |
What published fix windows look like across providers
Providers state fix windows differently, so compare the wording as well as the number. These are the figures each provider published on its own pages as read on 6 October 2026, from the Tomcat extended support providers comparison; check each page again before you sign.
| Provider | Published window | How it is worded |
|---|---|---|
| Perforce OpenLogic | 14 days for critical, 30 days for high | Service level objectives for long-term support, not an SLA |
| TuxCare | 14 days for CVSS 7.0 and above | A target on its Endless Lifecycle Support page |
| OSSeva | 48 hours Critical, 7 days High | The OSSeva patch SLA |
When extended support is the wrong answer
Do not buy extended support for a server that can simply move. A 9.0 server with NIO connectors can take Apache's 9.1.x branch as a minor upgrade, and a server whose application passes the jakarta migration can go to 10.1 or 11. Extended support earns its place for the server that cannot move before 31 March 2027: a third-party WAR nobody can rebuild, a vendor build pinned to 9.0, or an estate that needs the same contract across Tomcat, Spring and the data layer. The Tomcat 9 end of life checklist sorts servers into those groups in ten steps.
Red flags in a Tomcat extended support quote
- A coverage list of exact builds that does not include the build you run.
- A fix window with no start event, or "best effort" where a number should be.
- Coverage described only as "support", with no list of what is patched. Help-desk support and security patching are different things; ask which one the price buys.
- No statement about the JDK, the native connectors or embedded copies.
- Audit evidence offered as a letter only, with no per-release record.
How the questions were chosen
They are the points where Tomcat extended support contracts differ in practice: coverage by line or by build, the fix window and its start, delivery, evidence, scope exclusions and exit. OSSeva's answers come from its Tomcat extended support page and its PCI DSS evidence guide. Competitor figures are from the providers' own pages as read on 6 October 2026 and reproduced in the provider comparison. Apache dates are from tomcat.apache.org, read on 17 November 2026.
Frequently asked questions
What is Tomcat extended support?
Security patching for a Tomcat line the Apache project no longer releases fixes for, delivered as builds with the project's fixes backported. Tomcat 8.5 and 10.0 are already past end of life, and 9.0.x follows on 31 March 2027.
How is it different from the Apache 9.1.x branch?
Apache's 9.1.x branch carries the 9.x line to 31 December 2030 in its announcement, without the APR/native connectors. Extended support keeps the 9.0 line itself patched for servers that cannot make that move.
Does Tomcat extended support include the JDK?
Not from OSSeva. It patches Tomcat, and your Java vendor patches the JDK. See Java LTS end of life dates for each vendor's dates.
Which Tomcat versions need it first?
8.5 and 10.0, which have had no upstream fixes since 31 March 2024 and 31 October 2022. Then 9.0 after 31 March 2027, for servers that stay on it. Tomcat extended support lists the lines OSSeva covers.
Tags
Related articles
How to Choose a PostgreSQL Extended Support Vendor
November 17, 2026OperationsTomcat 9 end of life checklist: what to do before 31 March 2027
November 14, 2026OperationsTomcat Extended Support Providers (2026): Who Patches Apache Tomcat 8.5 and 9.0
October 6, 2026OperationsTomcat 9.1: Release Date, and When Tomcat 9.0 Ends (31 March 2027)
September 28, 2026ComplianceTomcat 9 after end of life in a PCI DSS 4.0 audit: what the assessor asks for
November 17, 2026SecurityApache Tomcat CVEs by Release: Which 9.0, 10.1 and 11.0 Version Fixes Each 2025 and 2026 CVE
October 5, 2026Get 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.
Prefer to talk or read more first?