# CVE-2025-66614: Apache Tomcat: Client certificate verification bypass due to virtual host mapping > Attackers can bypass client certificate authentication in Apache Tomcat by mismatching SNI and Host headers when multiple virtual hosts are configured. - **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Feb 2026 - **Updated:** 24 Mar 2026 - **Also known as:** BIT-tomcat-2025-66614, CLEANSTART-2026-BB54045, CLSA-2026-1773941493, CLSA-2026-1774261838, CLSA-2026-1774426919, CLSA-2026-1774431936, CLSA-2026-1774460133, CLSA-2026-1776818211, CLSA-2026-1777336750, DEBIAN-CVE-2025-66614, GHSA-fpj8-gq4v-p354, MINI-36fj-w928-qrv2, MINI-4jwm-r7wh-jr5w, MINI-gg93-r4x7-w7x6, MINI-hc3g-998w-hw4v, MINI-vg6g-mqrw-gmr3, MINI-x824-965g-5v65, ROOT-APP-MAVEN-CVE-2025-66614, UBUNTU-CVE-2025-66614 ## What is CVE-2025-66614? CVE-2025-66614 is a high-severity authentication bypass vulnerability in Apache Tomcat, published on 17 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-295 (Improper Certificate Validation), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2025-66614? 25 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, tomcat and org.apache.tomcat:tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.50 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.50 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.15 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.15 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0-M1 | 9.0.113 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0-M1 | 9.0.113 | | `tomcat` | Bitnami | From 8.5.0 | 9.0.113, 10.1.50, 11.0.15 | | `org.apache.tomcat:tomcat` | Maven | From 10.1.0-M1 | 10.1.50 | | `org.apache.tomcat:tomcat` | Maven | From 10.1.0-M1 | 10.1.50 | | `org.apache.tomcat:tomcat` | Maven | From 11.0.0-M1 | 11.0.15 | | `org.apache.tomcat:tomcat` | Maven | From 11.0.0-M1 | 11.0.15 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0-M1 | 9.0.113 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0-M1 | 9.0.113 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 10.1.0-M1 | 10.1.50 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 10.1.0-M1 | 10.1.50 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 11.0.0-M1 | 11.0.15 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 11.0.0-M1 | 11.0.15 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat:tomcat-coyote` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.0-M1 | 9.0.113 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.0-M1 | 9.0.113 | Products: Apache Tomcat. ## How do I fix CVE-2025-66614? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 10.1.50, 11.0.15 or 9.0.113. ## Is CVE-2025-66614 being exploited? There is no known exploitation of CVE-2025-66614 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-66614 and fix it if it is affected. What it is: CVE-2025-66614 is a high-severity authentication bypass vulnerability in Apache Tomcat, published on 17 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-66614 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.50 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.50 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.15 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.15 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0 up to 8.5.100; no fix listed - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0 up to 8.5.100; no fix listed - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0-M1; fixed in 9.0.113 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0-M1; fixed in 9.0.113 - tomcat (Bitnami): affected from 8.5.0; fixed in 9.0.113, 10.1.50, 11.0.15 - org.apache.tomcat:tomcat (Maven): affected from 10.1.0-M1; fixed in 10.1.50 - org.apache.tomcat:tomcat (Maven): affected from 10.1.0-M1; fixed in 10.1.50 - org.apache.tomcat:tomcat (Maven): affected from 11.0.0-M1; fixed in 11.0.15 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-66614/ (Markdown: https://insights.sbomify.com/CVE-2025-66614/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-66614 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-66614 - OSV: https://osv.dev/vulnerability/CVE-2025-66614 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-66614/ Summaries are generated and may contain mistakes; the official description above is the record.