Skip to content

Product

Apache Tomcat vulnerabilities

157 published CVES affecting Apache Tomcat, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
157
Critical
35
High
80
Medium
38
Low
4
Unscored
0
CISA KEV
6

Latest Apache Tomcat CVEs

Newest publication first · page 7 of 7

  1. CriticalCVSS 9.8 EPSS 7.8%

    In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the refactoring of the HTTP connectors introduced a regression in the send file processing. If the send file processing completed quickly, it was possible for the Processor to be added to the processor cache twice. This...

  2. HighCVSS 7.5 EPSS 8.3%

    In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a connection did not close streams associated with that connection that were currently waiting for a WINDOW_UPDATE before allowing the application to write more data. These wait...

  3. CriticalCVSS 9.1 EPSS 13.2%

    While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a Securi...

  4. CriticalCVSS 9.8 EPSS 90.3% CISA KEV added 2023-05-12 Exploited in the wild PoC

    Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 if JmxRemoteLifecycleListener is used and an attacker can reach JMX ports. The issue exists because this listener wasn't updated...

  5. HighCVSS 7.1 EPSS 39.6% Public exploit

    The code in Apache Tomcat 9.0.0.M1 to 9.0.0.M11, 8.5.0 to 8.5.6, 8.0.0.RC1 to 8.0.38, 7.0.0 to 7.0.72, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characte...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.