CVE-2025-66614: Apache Tomcat client certificate verification bypass via SNI mismatch

CVE-2025-66614 · Severity: critical · CVSS 9.1 · Published 2026-02-17

Apache Tomcat is a widely used web server for hosting Java applications. A security flaw allowed attackers to bypass required identity checks (client certificates) by providing mismatched server names during the initial connection. This could allow unauthorized users to access restricted areas of a web application that were supposed to be protected by digital certificates.

Technologies: Apache Tomcat, org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat-coyote (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2025-66614 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-66614 being exploited in the wild.
How severe is CVE-2025-66614?
Critical severity, with a CVSS score of 9.1, published 17 February 2026.
Which products and versions are affected?
Apache Tomcat 11.0.0-M1 to 11.0.14, 10.1.0-M1 to 10.1.49, 9.0.0-M1 to 9.0.112, 8.5.0 to 8.5.100; org.apache.tomcat:tomcat (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.15; org.apache.tomcat:tomcat-coyote (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.15; org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=11.0.0-M1,fixed=11.0.15.
Is there a fix for CVE-2025-66614?
Yes. org.apache.tomcat:tomcat (Maven): upgrade to 11.0.15 or later; org.apache.tomcat:tomcat-coyote (Maven): upgrade to 11.0.15 or later; org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 11.0.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-66614 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2025-66614?
Check whether you run Apache Tomcat, org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat-coyote (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.tomcat:tomcat (Maven): upgrade to 11.0.15 or later
    # set org.apache.tomcat:tomcat to 11.0.15 in your pom.xml or build.gradle
  • org.apache.tomcat:tomcat-coyote (Maven): upgrade to 11.0.15 or later
    # set org.apache.tomcat:tomcat-coyote to 11.0.15 in your pom.xml or build.gradle
  • org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 11.0.15 or later
    # set org.apache.tomcat.embed:tomcat-embed-core to 11.0.15 in your pom.xml or build.gradle

Technical details

Apache Tomcat does not verify that the host name provided in the TLS Server Name Indication (SNI) extension matches the host name in the HTTP Host header. In environments with multiple virtual hosts where one host requires client certificate authentication at the Connector level and another does not, an attacker can initiate a TLS handshake using the non-protected host's SNI but request the protected host via the HTTP header. This mismatch results in the bypass of certificate-based authentication. The vulnerability is mitigated if authentication is enforced at the web application level rather than the Connector. Patches are available in versions 11.0.15, 10.1.50, and 9.0.113.

Affected products

  • Apache Tomcat 11.0.0-M1 to 11.0.14, 10.1.0-M1 to 10.1.49, 9.0.0-M1 to 9.0.112, 8.5.0 to 8.5.100

Identifiers

  • CVE-2025-66614
  • GHSA-fpj8-gq4v-p354

Timeline

  • 2026-02-17: disclosed
  • 2026-02-17: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.