CVE-2025-66614

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2025-66614 has a CVSS score of 9.1 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.0.15, 10.1.50, 9.0.113); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-66614? CVE-2025-66614 is a medium-severity improper input validation vulnerability in org.apache.tomcat.embed:tomcat-embed-core (maven), affecting versions >= 11.0.0-M1, < 11.0.15. It is fixed in 11.0.15, 10.1.50, 9.0.113. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2025-66614? CVE-2025-66614 has a CVSS score of 9.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-66614?
   • org.apache.tomcat.embed:tomcat-embed-core (maven) (versions >= 11.0.0-M1, < 11.0.15)
   • org.apache.tomcat:tomcat (maven) (versions >= 11.0.0-M1, < 11.0.15)
   • org.apache.tomcat:tomcat-coyote (maven) (versions >= 11.0.0-M1, < 11.0.15)
4. Is there a fix for CVE-2025-66614? Yes. CVE-2025-66614 is fixed in 11.0.15, 10.1.50, 9.0.113. Upgrade to this version or later.
5. Is CVE-2025-66614 exploitable, and should I be worried? Whether CVE-2025-66614 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-66614 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-66614?
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 11.0.15 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 10.1.50 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.113 or later
   • Upgrade org.apache.tomcat:tomcat to 11.0.15 or later
   • Upgrade org.apache.tomcat:tomcat to 10.1.50 or later
   • Upgrade org.apache.tomcat:tomcat to 9.0.113 or later
   • Upgrade org.apache.tomcat:tomcat-coyote to 11.0.15 or later
   • Upgrade org.apache.tomcat:tomcat-coyote to 10.1.50 or later
   • Upgrade org.apache.tomcat:tomcat-coyote to 9.0.113 or later