Answer in brief
CVE-2025-66614 records a Medium severity (CVSS 9.1) vulnerability in Apache Tomcat - Client certificate verification bypass. The current sources do not mark it as known exploited. The current feed maps org.apache.tomcat.embed:tomcat-embed-core (maven), org.apache.tomcat.embed:tomcat-embed-core (maven), org.apache.tomcat.embed:tomcat-embed-core (maven), org.apache.tomcat.embed:tomcat-embed-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.apache.tomcat.embed:tomcat-embed-core (maven), org.apache.tomcat.embed:tomcat-embed-core (maven), org.apache.tomcat.embed:tomcat-embed-core (maven), org.apache.tomcat.embed:tomcat-embed-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=11.0.0-M1,<11.0.15 | 11.0.15 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=10.1.0-M1,<10.1.50 | 10.1.50 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | <9.0.113 | 9.0.113 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=9.0.0-M1,<9.0.113 | 9.0.113 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=8.5.0,<=8.5.100 | Not reported |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=11.0.0-M1 <11.0.15 | 11.0.15 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=10.1.0-M1 <10.1.50 | 10.1.50 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=9.0.0-M1 <9.0.113 | 9.0.113 |
| org.apache.tomcat.embed:tomcat-embed-coremaven | >=8.5.0 | Not reported |
| org.apache.tomcat:tomcatmaven | >=11.0.0-M1,<11.0.15 | 11.0.15 |
| org.apache.tomcat:tomcatmaven | >=10.1.0-M1,<10.1.50 | 10.1.50 |
| org.apache.tomcat:tomcatmaven | <9.0.113 | 9.0.113 |
| org.apache.tomcat:tomcatmaven | >=9.0.0-M1,<9.0.113 | 9.0.113 |
| org.apache.tomcat:tomcatmaven | >=8.5.0,<=8.5.100 | Not reported |
| org.apache.tomcat:tomcatmaven | >=11.0.0-M1 <11.0.15 | 11.0.15 |
| org.apache.tomcat:tomcatmaven | >=10.1.0-M1 <10.1.50 | 10.1.50 |
| org.apache.tomcat:tomcatmaven | >=9.0.0-M1 <9.0.113 | 9.0.113 |
| org.apache.tomcat:tomcatmaven | >=8.5.0 | Not reported |
| org.apache.tomcat:tomcat-coyotemaven | >=11.0.0-M1,<11.0.15 | 11.0.15 |
| org.apache.tomcat:tomcat-coyotemaven | >=10.1.0-M1,<10.1.50 | 10.1.50 |
| org.apache.tomcat:tomcat-coyotemaven | <9.0.113 | 9.0.113 |
| org.apache.tomcat:tomcat-coyotemaven | >=9.0.0-M1,<9.0.113 | 9.0.113 |
| org.apache.tomcat:tomcat-coyotemaven | >=8.5.0,<=8.5.100 | Not reported |
| org.apache.tomcat:tomcat-coyotemaven | >=11.0.0-M1 <11.0.15 | 11.0.15 |
| org.apache.tomcat:tomcat-coyotemaven | >=10.1.0-M1 <10.1.50 | 10.1.50 |
| org.apache.tomcat:tomcat-coyotemaven | >=9.0.0-M1 <9.0.113 | 9.0.113 |
| org.apache.tomcat:tomcat-coyotemaven | >=8.5.0 | Not reported |
Published upstream
Feb 17, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.