EOL Apache Tomcat Security Patches — Versions 8.5, 9.0

php2shell patches (CVE-2026-109618 and CVE-2026-109619) for EOL PHP are out now. With sales replies slower than usual due to high demand, the fastest route to patched packages is to buy ELS for Runtimes online (opens in new tab). Read the patch FAQ

If your Apache Tomcat version has reached the end of support, it no longer receives critical security updates or fixes.

Running an unsupported Tomcat version leaves your applications vulnerable to exploits such as authentication bypasses, session hijacking, and web application attacks – potentially compromising sensitive data.

Tomcat upgrades aren’t just version bumps – they introduce configuration shifts,
servlet API changes, and potential incompatibilities with existing deployments.

Don’t let a forced upgrade break your setup – stay protected with ELS from TuxCare.

With Endless Lifecycle Support,

you can:

Minimize Security Risks

Get as much time as you need of security patches for Apache Tomcat vulnerabilities from an experienced team.

Preserve Compatibility

Avoid code refactoring and keep your Apache Tomcat applications running smoothly for years to come.

Ensure Compliance

Gain 14-day SLAs for security fixes and establish transparency with a detailed SBOM.

Apache Tomcat core components that we currently support:

  • Coyote (HTTP connector)
  • Catalina (servlet engine)
  • Jasper (JSP engine)
  • Cluster

Contact us if you need support for
additional components

Why TuxCare?

15 years of proven excellence in open-source patching have created highly
automated processes and systems, providing:

Extensive Coverage of Open-Source Technologies

We provide long-term security across your entire stack, supporting a wide and continually expanding set of open-source projects, libraries, and runtimes – all from a single, trusted partner.

Efficiencies in Build Chains and Testing

We utilize advanced automation across CVE discovery, backporting, building, and release workflows to accelerate delivery and ensure the highest possible quality of security patches.

Identification and Patching of Transitive Dependencies

We go beyond surface-level scanning to uncover and fix hidden vulnerabilities deep in your dependency trees, securing the entire software supply chain with precision and scale.

Fast and Consistent Delivery of Patches with Supporting SLAs

Automated pipelines and mature workflows ensure rapid, reliable patch delivery backed by SLAs – giving you confidence in your risk management and compliance posture.

We’ve Been Powering Enterprise-Grade Patching At
Unprecedented Scale – and We're Just Getting Started

2,700+
Enterprise Clients

70,000+Packages Curated

420,000+
Patches Delivered

14,000+
Vulnerabilities Fixed

11,000+
Kernels Supported

70+
Linux Distro Versions Supported

Long-Term Security After Standard Support Ends

TuxCare ELS continues to deliver enduring security for your distro, language, or software development framework for as many years as your organization requires

Frequently Asked Questions

Tomcat 7.0 ended in March 2021 and Tomcat 8.5 ended March 31, 2024. Once a branch retires, the Apache Tomcat project publishes nothing further for it, security releases included. ELS for Apache Tomcat continues patching retired branches and specific pinned builds.

Tomcat 7.0.109, 8.5.100, 9.0.46, 9.0.50, 9.0.75, 9.0.83, 9.0.87, 9.0.90, 9.0.100, 10.1.18, and 10.1.42 — covering both fully retired branches and specific pinned 9.0.x and 10.1.x builds that teams can't move off. Patches target core components including Catalina, Coyote, and Jasper.

Yes. Unsupported middleware is a standing finding under PCI DSS, HIPAA, and FedRAMP. ELS keeps CVEs closed in the version you run, and the 14-day target for CVSS 7.0+ fixes sits inside PCI DSS's 30-day remediation requirement.

Yes. Patches apply within the same Tomcat version, so connector tuning, valves, realms, custom server.xml, and deployed WARs stay as they are — exactly what a major-version jump puts at risk.

Yes. Tomcat ships both as a standalone server and as library artifacts. Server builds come from TuxCare's Nexus els_java repository as .tar.gz for Linux or .zip for Windows; Maven and Gradle projects resolve the same patched artifacts as dependencies, which covers embedded Tomcat in Spring Boot-style applications.

No. Installation needs JDK 7 or later with JAVA_HOME set — the JDK your application already uses. If that JDK is itself out of support, ELS for OpenJDK covers 7, 8, 11, and 17.

Continue running your applications on end-
of-life Apache Tomcat versions without
worrying about unpatched security
vulnerabilities