Skip to content

[GHSA-fpj8-gq4v-p354] Apache Tomcat - Client certificate verification bypass #7663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
advisory-database merged 1 commit into from
Jun 12, 2026
Merged

[GHSA-fpj8-gq4v-p354] Apache Tomcat - Client certificate verification bypass #7663

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions advisories/github-reviewed/2026/02/GHSA-fpj8-gq4v-p354/GHSA-fpj8-gq4v-p354.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,14 @@
{
"schema_version": "1.4.0",
"id": "GHSA-fpj8-gq4v-p354",
"modified": "2026-03-11T20:38:06Z",
"modified": "2026-03-11T20:38:07Z",
"published": "2026-02-17T21:31:13Z",
"aliases": [
"CVE-2025-66614"
],
"summary": "Apache Tomcat - Client certificate verification bypass",
"details": "Improper Input Validation vulnerability.\n\nThis 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.\n\nThe 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.\n\nThe 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.\n\nUsers 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.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
},
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
Expand Down Expand Up @@ -136,7 +132,7 @@
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.tomcat:tomcat-catalina"
"name": "org.apache.tomcat:tomcat-coyote"
},
"ranges": [
{
Expand All @@ -155,7 +151,7 @@
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.tomcat:tomcat-catalina"
"name": "org.apache.tomcat:tomcat-coyote"
},
"ranges": [
{
Expand All @@ -174,7 +170,7 @@
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.tomcat:tomcat-catalina"
"name": "org.apache.tomcat:tomcat-coyote"
},
"ranges": [
{
Expand Down
Loading