Approved changes feed: RSS · Atom

cpe:2.3:a:apache:tomcat:11.0.0:milestone26:*:*:*:*:*:*

part: a version: 11.0.0 update: milestone26

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductTomcat (caaa56d3-0cc4-5735-aab9-a3a1a7f4dc56)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/tomcat purl2cpe 2026-06-01 10:14:26.993956
pkg:github/apache/tomcat purl2cpe 2026-06-01 10:14:26.993957
pkg:maven/org.apache.tomcat/tomcat purl2cpe 2026-06-01 10:14:26.993958
pkg:rpm/fedora/tomcat purl2cpe 2026-06-01 10:14:26.993960
pkg:rpm/opensuse/tomcat purl2cpe 2026-06-01 10:14:26.993961

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-34500 vulnerable 2026-06-08 07:59:12.647117 Apache Tomcat: OCSP checks sometimes soft-fail with FFM even when soft-fail is disabled
CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.20, from 10.1.22 through 10.1.53, from 9.0.92 through 9.0.116. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue.
Published: 2026-04-09T19:36:52.857Z
Updated: 2026-04-10T14:22:31.310Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-24734 vulnerable 2026-06-08 07:51:18.087260 Apache Tomcat Native, Apache Tomcat: OCSP revocation bypass
Improper Input Validation vulnerability in Apache Tomcat Native, Apache Tomcat. When using an OCSP responder, Tomcat Native (and Tomcat's FFM port of the Tomcat Native code) did not complete verification or freshness checks on the OCSP response which could allow certificate revocation to be bypassed. This issue affects Apache Tomcat Native:  from 1.3.0 through 1.3.4, from 2.0.0 through 2.0.11; Apache Tomcat: from 11.0.0-M1 through 11.0.17, from 10.1.0-M7 through 10.1.51, from 9.0.83 through 9.0.114. The following versions were EOL at the time the CVE was created but are known to be affected: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39. Older EOL versions are not affected. Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue. Apache Tomcat users are recommended to upgrade to versions 11.0.18 or later, 10.1.52 or later or 9.0.115 or later which fix the issue.
Published: 2026-02-17T18:53:12.228Z
Updated: 2026-07-15T13:48:07.714Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-24733 vulnerable 2026-06-08 07:51:18.062863 Apache Tomcat: Security constraint bypass with HTTP/0.9
Improper Input Validation vulnerability in Apache Tomcat. Tomcat did not limit HTTP/0.9 requests to the GET method. If a security constraint was configured to allow HEAD requests to a URI but deny GET requests, the user could bypass that constraint on GET requests by sending a (specification invalid) HEAD request using HTTP/0.9. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0.M1 through 9.0.112. Older, EOL versions are also affected. Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or later, which fixes the issue.
Published: 2026-02-17T18:50:43.871Z
Updated: 2026-03-11T15:19:30.867Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-66614 vulnerable 2026-06-08 07:41:19.331527 Apache Tomcat: Client certificate verification bypass due to virtual host mapping
Improper Input Validation vulnerability. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0-M1 through 9.0.112. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 through 8.5.100. Older EOL versions are not affected. Tomcat did not validate that the host name provided via the SNI extension was the same as the host name provided in the HTTP host header field. If Tomcat was configured with more than one virtual host and the TLS configuration for one of those hosts did not require client certificate authentication but another one did, it was possible for a client to bypass the client certificate authentication by sending different host names in the SNI extension and the HTTP host header field. The vulnerability only applies if client certificate authentication is only enforced at the Connector. It does not apply if client certificate authentication is enforced at the web application. Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or later, which fix the issue.
Published: 2026-02-17T18:48:30.577Z
Updated: 2026-03-24T09:46:33.159Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-52317 vulnerable 2026-06-08 06:52:14.793873 Apache Tomcat: Request/response mix-up with HTTP/2
Incorrect object re-cycling and re-use vulnerability in Apache Tomcat. Incorrect recycling of the request and response used by HTTP/2 requests could lead to request and/or response mix-up between users. This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.0-M26, from 10.1.27 through 10.1.30, from 9.0.92 through 9.0.95. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fixes the issue.
Published: 2024-11-18T11:36:51.963Z
Updated: 2025-01-24T20:03:10.485Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-52316 vulnerable 2026-06-08 06:52:14.787803 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.