{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Apache Tomcat",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThanOrEqual": "11.0.14",
              "status": "affected",
              "version": "11.0.0-M1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "10.1.49",
              "status": "affected",
              "version": "10.1.0-M1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "9.0.112",
              "status": "affected",
              "version": "9.0.0-M1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "8.5.100",
              "status": "affected",
              "version": "8.5.0",
              "versionType": "semver"
            },
            {
              "lessThan": "8.5.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eImproper Input Validation vulnerability.\u003c/p\u003e\u003cp\u003eThis 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.\u003c/p\u003eThe following versions were EOL at the time the CVE was created but are \nknown to be affected: 8.5.0 through 8.5.100. Older EOL versions are not affected.\u003cbr\u003e\u003cp\u003eTomcat did not validate that the host name provided via the SNI \nextension was the same as the host name provided in the HTTP host header \nfield. If Tomcat was configured with more than one virtual host and the \nTLS configuration for one of those hosts did not require client \ncertificate authentication but another one did, it was possible for a \nclient to bypass the client certificate authentication by sending \ndifferent host names in the SNI extension and the HTTP host header field.\n\u003cbr\u003e\n\u003cbr\u003eThe vulnerability only applies if client certificate authentication is \nonly enforced at the Connector. It does not apply if client certificate \nauthentication is enforced at the web application.\u003cbr\u003e\u003c/p\u003e\u003cp\u003eUsers 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.\u003c/p\u003e"
            }
          ],
          "value": "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 \nknown to be affected: 8.5.0 through 8.5.100. Older EOL versions are not affected.\nTomcat did not validate that the host name provided via the SNI \nextension was the same as the host name provided in the HTTP host header \nfield. If Tomcat was configured with more than one virtual host and the \nTLS configuration for one of those hosts did not require client \ncertificate authentication but another one did, it was possible for a \nclient to bypass the client certificate authentication by sending \ndifferent host names in the SNI extension and the HTTP host header field.\n\n\n\nThe vulnerability only applies if client certificate authentication is \nonly enforced at the Connector. It does not apply if client certificate \nauthentication is enforced at the web application.\n\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."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "moderate"
            },
            "type": "Textual description of severity"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-20",
              "description": "CWE-20 Improper Input Validation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-02-17T18:48:30.577Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/vw6lxtlh2qbqwpb61wd3sv1flm2nttw7"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Apache Tomcat: Client certificate verification bypass due to virtual host mapping",
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2025-66614",
    "datePublished": "2026-02-17T18:48:30.577Z",
    "dateReserved": "2025-12-05T11:54:31.778Z",
    "dateUpdated": "2026-02-17T18:48:30.577Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-66614\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2026-02-17T19:21:55.310\",\"lastModified\":\"2026-02-18T17:51:53.510\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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 \\nknown to be affected: 8.5.0 through 8.5.100. Older EOL versions are not affected.\\nTomcat did not validate that the host name provided via the SNI \\nextension was the same as the host name provided in the HTTP host header \\nfield. If Tomcat was configured with more than one virtual host and the \\nTLS configuration for one of those hosts did not require client \\ncertificate authentication but another one did, it was possible for a \\nclient to bypass the client certificate authentication by sending \\ndifferent host names in the SNI extension and the HTTP host header field.\\n\\n\\n\\nThe vulnerability only applies if client certificate authentication is \\nonly enforced at the Connector. It does not apply if client certificate \\nauthentication is enforced at the web application.\\n\\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.\"},{\"lang\":\"es\",\"value\":\"Vulnerabilidad de validaci\u00f3n de entrada inadecuada.\\n\\nEste problema afecta a Apache Tomcat: desde 11.0.0-M1 hasta 11.0.14, desde 10.1.0-M1 hasta 10.1.49, desde 9.0.0-M1 hasta 9.0.112.\\n\\nLas siguientes versiones estaban al final de su vida \u00fatil (EOL) en el momento en que se cre\u00f3 el CVE, pero se sabe que est\u00e1n afectadas: 8.5.0 hasta 8.5.100. Las versiones EOL m\u00e1s antiguas no est\u00e1n afectadas.\\nTomcat no validaba que el nombre de host proporcionado a trav\u00e9s de la extensi\u00f3n SNI fuera el mismo que el nombre de host proporcionado en el campo de encabezado de host HTTP. Si Tomcat estaba configurado con m\u00e1s de un host virtual y la configuraci\u00f3n TLS para uno de esos hosts no requer\u00eda autenticaci\u00f3n de certificado de cliente pero otro s\u00ed lo hac\u00eda, era posible para un cliente omitir la autenticaci\u00f3n de certificado de cliente enviando diferentes nombres de host en la extensi\u00f3n SNI y el campo de encabezado de host HTTP.\\n\\nLa vulnerabilidad solo se aplica si la autenticaci\u00f3n de certificado de cliente solo se impone en el Conector. No se aplica si la autenticaci\u00f3n de certificado de cliente se impone en la aplicaci\u00f3n web.\\n\\nSe recomienda a los usuarios actualizar a la versi\u00f3n 11.0.15 o posterior, 10.1.50 o posterior o 9.0.113 o posterior, que solucionan el problema.\"}],\"metrics\":{},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-20\"}]}],\"references\":[{\"url\":\"https://lists.apache.org/thread/vw6lxtlh2qbqwpb61wd3sv1flm2nttw7\",\"source\":\"security@apache.org\"}]}}"
  }
}