CVE-2025-66614: Apache Tomcat: Client certificate verification bypass due to virtual host mapping

Published Feb 17, 2026
·
Updated

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.

Affected Software

87 affected componentsFixes available
Apache Tomcat>=11.0.0-M1<=11.0.14, >=10.1.0-M1<=10.1.49, >=9.0.0-M1<=9.0.112, >=8.5.0<=8.5.100
maven/org.apache.tomcat:tomcat-catalina<9.0.112
9.0.112
maven/org.apache.tomcat:tomcat-catalina>=10.1.0-M1<10.1.49
10.1.49
maven/org.apache.tomcat:tomcat-catalina>=11.0.0-M1<11.0.14
11.0.14
maven/org.apache.tomcat:tomcat<9.0.112
9.0.112
maven/org.apache.tomcat:tomcat>=10.1.0-M1<10.1.49
10.1.49
maven/org.apache.tomcat:tomcat>=11.0.0-M1<11.0.14
11.0.14
maven/org.apache.tomcat.embed:tomcat-embed-core<9.0.112
9.0.112
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1<10.1.49
10.1.49
maven/org.apache.tomcat.embed:tomcat-embed-core>=11.0.0-M1<11.0.14
11.0.14
Apache Tomcat>=9.0.1<9.0.113
Apache Tomcat>=10.1.1<10.1.50
Apache Tomcat>=11.0.1<11.0.15
Apache Tomcat=9.0.0-milestone1
Apache Tomcat=9.0.0-milestone10
Apache Tomcat=9.0.0-milestone11
Apache Tomcat=9.0.0-milestone12
Apache Tomcat=9.0.0-milestone13
Apache Tomcat=9.0.0-milestone14
Apache Tomcat=9.0.0-milestone15
Apache Tomcat=9.0.0-milestone16
Apache Tomcat=9.0.0-milestone17
Apache Tomcat=9.0.0-milestone18
Apache Tomcat=9.0.0-milestone19
Apache Tomcat=9.0.0-milestone2
Apache Tomcat=9.0.0-milestone20
Apache Tomcat=9.0.0-milestone21
Apache Tomcat=9.0.0-milestone22
Apache Tomcat=9.0.0-milestone23
Apache Tomcat=9.0.0-milestone24
Apache Tomcat=9.0.0-milestone25
Apache Tomcat=9.0.0-milestone26
Apache Tomcat=9.0.0-milestone27
Apache Tomcat=9.0.0-milestone3
Apache Tomcat=9.0.0-milestone4
Apache Tomcat=9.0.0-milestone5
Apache Tomcat=9.0.0-milestone6
Apache Tomcat=9.0.0-milestone7
Apache Tomcat=9.0.0-milestone8
Apache Tomcat=9.0.0-milestone9
Apache Tomcat=10.1.0-milestone1
Apache Tomcat=10.1.0-milestone10
Apache Tomcat=10.1.0-milestone11
Apache Tomcat=10.1.0-milestone12
Apache Tomcat=10.1.0-milestone13
Apache Tomcat=10.1.0-milestone14
Apache Tomcat=10.1.0-milestone15
Apache Tomcat=10.1.0-milestone16
Apache Tomcat=10.1.0-milestone17
Apache Tomcat=10.1.0-milestone18
Apache Tomcat=10.1.0-milestone19
Apache Tomcat=10.1.0-milestone2
Apache Tomcat=10.1.0-milestone20
Apache Tomcat=10.1.0-milestone3
Apache Tomcat=10.1.0-milestone4
Apache Tomcat=10.1.0-milestone5
Apache Tomcat=10.1.0-milestone6
Apache Tomcat=10.1.0-milestone7
Apache Tomcat=10.1.0-milestone8
Apache Tomcat=10.1.0-milestone9
Apache Tomcat=11.0.0-milestone1
Apache Tomcat=11.0.0-milestone10
Apache Tomcat=11.0.0-milestone11
Apache Tomcat=11.0.0-milestone12
Apache Tomcat=11.0.0-milestone13
Apache Tomcat=11.0.0-milestone14
Apache Tomcat=11.0.0-milestone15
Apache Tomcat=11.0.0-milestone16
Apache Tomcat=11.0.0-milestone17
Apache Tomcat=11.0.0-milestone18
Apache Tomcat=11.0.0-milestone19
Apache Tomcat=11.0.0-milestone2
Apache Tomcat=11.0.0-milestone20
Apache Tomcat=11.0.0-milestone21
Apache Tomcat=11.0.0-milestone22
Apache Tomcat=11.0.0-milestone23
Apache Tomcat=11.0.0-milestone24
Apache Tomcat=11.0.0-milestone25
Apache Tomcat=11.0.0-milestone26
Apache Tomcat=11.0.0-milestone3
Apache Tomcat=11.0.0-milestone4
Apache Tomcat=11.0.0-milestone5
Apache Tomcat=11.0.0-milestone6
Apache Tomcat=11.0.0-milestone7
Apache Tomcat=11.0.0-milestone8
Apache Tomcat=11.0.0-milestone9
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 9.0.112
  2. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 10.1.49
  3. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 11.0.14
  4. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.112
  5. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.49
  6. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.14
  7. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.112
  8. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 10.1.49
  9. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 11.0.14
  10. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.15
  11. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.50
  12. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.113
  13. Configuration

    If you use multiple virtual hosts with differing TLS client-certificate requirements, ensure client certificate authentication is enforced at the web application (this issue does not apply if client certificate authentication is enforced at the web application; it only applies when client certificate authentication is only enforced at the Connector).

    Apache Tomcat client certificate authentication enforcement = enforce at the web application
  14. Compensating control

    For deployments with multiple virtual hosts where one TLS configuration does not require client certificate authentication, restrict access so that the vulnerable virtual-host mapping condition cannot be exercised (e.g., align TLS client-certificate requirements across virtual hosts, or otherwise prevent clients from reaching a host whose TLS does not enforce client certificates when others do).

Event History

Feb 17, 2026
CVE Published
via MITRE·06:48 PM
Data Sourced
via MITRE·06:48 PM
DescriptionWeakness
Data Sourced
via NVD·07:21 PM
DescriptionWeakness
Data Sourced
via NVD·07:21 PM
SeverityAffected Software
Data Sourced
via Red Hat·08:04 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-66614?

CVE-2025-66614 has a high severity due to the potential for client certificate verification bypass.

2

How do I fix CVE-2025-66614?

To fix CVE-2025-66614, upgrade to Apache Tomcat version 11.0.14, 10.1.49, or 9.0.112.

3

Which versions of Apache Tomcat are affected by CVE-2025-66614?

CVE-2025-66614 affects Apache Tomcat versions from 11.0.0-M1 through 11.0.14, 10.1.0-M1 through 10.1.49, and 9.0.0-M1 through 9.0.112.

4

What kind of vulnerability is CVE-2025-66614?

CVE-2025-66614 is categorized as an Improper Input Validation vulnerability.

5

Can CVE-2025-66614 affect my application if I use an affected version of Tomcat?

Yes, using an affected version of Tomcat leaves your application vulnerable to client certificate verification bypass.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203