Back to blog

OSSeva Blog

Security

Finding embedded end-of-life Tomcat inside vendor appliances and applications

7 min read

Where embedded Tomcat hides, and who can patch it

End-of-life Tomcat sits in four places, and only the first two are yours to patch: a standalone install, a Spring Boot or other fat jar, a container image, and a vendor product that bundles its own copy. A scanner or an audit finds the old version in a place your server inventory never listed. The table maps each place to the way to find it and the party that owns the fix. For the copies you do own, Tomcat extended support keeps ended lines patched.

Where it hidesHow to find itWho can patch it
Standalone Tomcat you installedLook for a running process with -Dcatalina.base, or run $CATALINA_HOME/bin/version.sh.You, or an extended support provider for an ended line
Spring Boot or other fat jarList the jar's contents for a tomcat-embed-core library, or read the dependency tree of the build.You, by upgrading the framework or setting the Tomcat version; an extended support provider where the framework line has ended
Container imageSearch the image's file system for catalina.jar and tomcat-embed-core, or generate an SBOM for the image.You, by rebuilding from a patched base or a patched Tomcat build
Vendor appliance or packaged productSearch the install directory for catalina.jar, check the error page footer, and compare with the vendor's release notes.The vendor only. You can ask, escalate and compensate, but you cannot swap the component

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

Spring Boot extended support: what is covered

How do you find embedded Tomcat on a host?

Search for the file that every Tomcat copy ships, catalina.jar or tomcat-embed-core, then read its version. A server inventory built from package managers misses all of these, because the vendor installed the files itself.

  1. Search the file system. On Linux, find / -name "catalina*.jar" -o -name "tomcat-embed-core*.jar" 2>/dev/null. The version is usually in the jar name for embedded copies.
  2. Read the version from the jar. Tomcat's own version.sh runs the org.apache.catalina.util.ServerInfo class from lib/catalina.jar; the same class prints the version for a copy you found by hand.
  3. Look inside fat jars. Spring Boot executable jars carry their libraries under BOOT-INF/lib, so listing the jar shows the embedded Tomcat version without running the application.
  4. Check the error page. Tomcat's error report valve shows the server version on error pages unless showServerInfo is set to false; its default is true (Tomcat 9 configuration reference, read 17 November 2026). A scanner finds the same footer.
  5. Check running processes and listeners. A Java process whose classpath includes catalina.jar, listening on 8080 or 8443, is Tomcat even when the product's name says something else.
  6. Generate an SBOM for each image and application. It lists the Tomcat libraries with versions, which turns a one-off hunt into a repeatable check.

Which embedded Tomcat versions are already end of life?

Tomcat 7.0, 8.5 and 10.0 are past end of life today, and 9.0 follows on 31 March 2027. Any of these inside a product you did not install belongs on your end-of-life list.

Tomcat lineEnd of supportStatus on 17 Nov 2026
7.0.x31 March 2021Ended (Tomcat 7)
8.5.x31 March 2024Ended; final release 8.5.100 (Tomcat 8.5 end of life)
10.0.x31 October 2022Ended; final release 10.0.27 (Tomcat 10.0)
9.0.x31 March 2027Supported until then (Tomcat 9 EOL)
10.1.x and 11.0.xNo date announcedSupported

Sources: Apache's end of support announcement for 9.0.x and the Which Version page on tomcat.apache.org, and endoflife.date/tomcat, all read on 17 November 2026. Even a supported line is only safe on a recent release: Apache's 9.x security page lists 58 advisory entries fixed between 9.0.113 and 9.0.123, so an appliance on an old 9.0.x build is behind even though 9.0 is supported.

What to do when the Tomcat is inside a vendor appliance

Treat it as a vendor finding with a deadline, not as a server you can patch. Do these in order:

  1. Record the product, the Tomcat version and the connectors it exposes. An AJP listener matters: Apache lists CVE-2020-1938, an AJP request injection rated Important, as fixed in 9.0.31.
  2. Ask the vendor in writing which Tomcat version the product ships, which release moves it to a supported line, and the date. Keep the answer.
  3. Reduce exposure while you wait: restrict network access to the Tomcat ports, and turn off a listener the product does not need if the vendor allows it. Hiding the version string with showServerInfo only reduces fingerprinting; it does not fix a vulnerability.
  4. Put the finding in your annual technology review with an owner and a date. PCI DSS 12.3.4 asks for a management-approved plan for outdated technology (see Tomcat 9 in a PCI DSS 4.0 audit).
  5. If the vendor has no plan, the options are to replace the product or to accept the risk in writing.

Where OSSeva can and cannot help with embedded Tomcat

OSSeva can patch Tomcat you run and Tomcat embedded in a Spring Boot application it covers; it cannot replace the Tomcat inside a sealed vendor appliance. OSSeva ships signed Tomcat builds for 8.5, 9.0, 10.0, 10.1 and 11, and embedded Tomcat in a Spring Boot application covered by OSSeva is part of that Spring Boot coverage. A vendor's appliance is the vendor's build. OSSeva does not patch the JDK either. If an inventory pass turns up Tomcat you do own, Tomcat extended support covers it, and the Tomcat 9 end of life checklist turns the findings into a plan.

What to record for each copy you find

FieldExample entryWhy
Host and productHost name, product, vendor, versionTies the finding to someone who can act
Tomcat version and line9.0.x, 8.5.xSets the end-of-life date
Java version8, 11, 17Decides which Tomcat line can run
Connectors exposedHTTP, HTTPS, AJPDecides the exposure and the 9.1.x move
Patch ownerYou, vendor, extended support providerSays who must act
Date and actionVendor reply due, replace by a dateTurns a finding into a plan

Frequently asked questions

How do I know if a vendor product includes Tomcat?

Search its install directory for catalina.jar or tomcat-embed-core jars, look for a Java process with catalina.jar on the classpath, and check the error page footer. A vendor's release notes or support team can confirm the version.

Can I patch Tomcat inside an appliance myself?

Not safely. The appliance's vendor tests and supports its own build, so replacing files inside it can break the product and its support. Ask the vendor for a release that ships a supported Tomcat line.

Does a vulnerability scanner find embedded Tomcat?

Often, by the version string on the error page or in the jar name, though a scanner can both miss copies and flag a version that carries a backported fix. Confirm findings against the vendor's own statement.

Is Tomcat embedded in a Spring Boot application covered by extended support?

Yes where the application is covered by OSSeva's Spring Boot coverage. The embedded Tomcat is included in it, with no separate engagement. See Tomcat extended support for the standalone lines.

Tags

Apache TomcatEnd of LifeEmbedded TomcatSpring BootVulnerability Management

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