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.
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.
Update org.apache.tomcat.embed:tomcat-embed-core to 11.0.15; org.apache.tomcat.embed:tomcat-embed-core to 10.1.50; org.apache.tomcat.embed:tomcat-embed-core to 9.0.113; org.apache.tomcat:tomcat to 11.0.15; org.apache.tomcat:tomcat to 10.1.50; org.apache.tomcat:tomcat to 9.0.113; org.apache.tomcat:tomcat-coyote to 11.0.15; org.apache.tomcat:tomcat-coyote to 10.1.50; org.apache.tomcat:tomcat-coyote to 9.0.113 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanApache Tomcat - Client certificate verification bypass affects 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:tomcat (maven), org.apache.tomcat:tomcat (maven), org.apache.tomcat:tomcat (maven), org.apache.tomcat:tomcat-coyote (maven), org.apache.tomcat:tomcat-coyote (maven), org.apache.tomcat:tomcat-coyote (maven). Severity is medium. 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.
AI coding agents often install or upgrade packages automatically in maven. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| 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: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:tomcat-coyote |
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate org.apache.tomcat.embed:tomcat-embed-core to 11.0.15; org.apache.tomcat.embed:tomcat-embed-core to 10.1.50; org.apache.tomcat.embed:tomcat-embed-core to 9.0.113; org.apache.tomcat:tomcat to 11.0.15; org.apache.tomcat:tomcat to 10.1.50; org.apache.tomcat:tomcat to 9.0.113; org.apache.tomcat:tomcat-coyote to 11.0.15; org.apache.tomcat:tomcat-coyote to 10.1.50; org.apache.tomcat:tomcat-coyote to 9.0.113 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanApache Tomcat - Client certificate verification bypass affects 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:tomcat (maven), org.apache.tomcat:tomcat (maven), org.apache.tomcat:tomcat (maven), org.apache.tomcat:tomcat-coyote (maven), org.apache.tomcat:tomcat-coyote (maven), org.apache.tomcat:tomcat-coyote (maven). Severity is medium. 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.
AI coding agents often install or upgrade packages automatically in maven. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| 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: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:tomcat-coyote |
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| >=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 |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
| >=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 |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.