CWE-297 · weakness in Cryptography
Improper Validation of Certificate with Host Mismatch
101 CVEs
Every dot is a CVE; the named ones are the most at risk. Red is exploited in the wild.
Every one of the 101 is a mark on the map. Named now: 1 to 26, most at risk first.
- The Serf RA layer in Apache Subversion 1.4.0 through 1.7.x before 1.7.18 and 1.8.x before 1.8.10 does not properly handle wildcards in the Common Name (CN) or subjectAltName field…
- A weakness was found in postgresql-jdbc before version 42.2.5. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to th…
- SMTPS server hostname not checked when making TLS connection to SMTPS server
- Incorrect validation of the TLS SNI hostname in osquery versions after 2.9.0 and before 4.2.0 could allow an attacker to MITM osquery traffic in the absence of a configured root c…
- TLS certificate check bypass with mbedTLS
- A flaw was found in rsync in versions since 3.2.0pre1. Rsync improperly validates certificate with host mismatch vulnerability. A remote, unauthenticated attacker could exploit th…
- Existing TLS connections can be reused without checking remote hostname
- Splunk Enterprise lacked TLS host name validation
- A flaw was found in Keycloak in versions before 10.0.0, where it does not perform the TLS hostname verification while sending emails using the SMTP server. This flaw allows an att…
- The (1) HttpResource and (2) FileBackedHttpResource implementations in Shibboleth Identity Provider (IdP) before 2.4.1 and OpenSAML Java 2.6.2 do not verify that the server hostna…
- Improper Validation of Certificate with Host Mismatch in Java-WebSocket
- An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS) 2.73.6) and before BC FIPS TLS Java 1.0.19.…
- Apache Log4j Core: Missing TLS hostname verification in Socket appender
- redirect to SFTP or SCP bypasses host verification
- Disabled hostname verification and accepting self-signed certificates
- An exploitable vulnerability exists in the remote control functionality of Circle with Disney running firmware 2.0.1. SSL certificates for specific domain names can cause the rcli…
- PKId in Juniper Junos OS before 12.1X44-D52, 12.1X46 before 12.1X46-D37, 12.1X47 before 12.1X47-D30, 12.3 before 12.3R12, 12.3X48 before 12.3X48-D20, 13.3 before 13.3R10, 14.1 bef…
- An exploitable vulnerability exists in the remote control functionality of Circle with Disney running firmware 2.0.1. SSL certificates for specific domain names can cause the gocl…
- An issue was discovered in the methods push.lite.avtech.com.AvtechLib.GetHttpsResponse and push.lite.avtech.com.Push_HttpService.getNewHttpClient in AVTECH EagleEyes 2.0.0. The me…
- Apache Thrift: TSSLTransportFactory.java hostname verification
- Apache Ranger: Clients accept TLS certificates issued for other hostnames
- Apache Log4j Core: verifyHostName attribute silently ignored in TLS configuration, allowing hostname verification bypass
- Potentially, SAP Cloud Connector, version - 2.0 communication with the backend is accepted without sufficient validation of the certificate.
- libssh global known_hosts override
- SSLContext.wrap_bio() missing validation of server_hostname parameter
- Apache Ranger: Hostname verification bypass in NiFiRegistryClient
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.