JetBrains ReSharper versions prior to 2026.3 do not verify server host names during certificate validation, leading to improper validation of certificates with host mismatches. This vulnerability is identified as CWE-297. It has a low CVSS score of 3.7 and was fixed in version 2026.3.
CVE-2026-87758 is a vulnerability in Apache TomEE where the remote EJB client fails to verify that the server's hostname matches the TLS certificate. This improper validation allows an attacker intercepting network traffic to impersonate the server and potentially read or modify sensitive data such as credentials and invocation information. The issue is fixed in Apache TomEE versions 10.3.0 and 11.0.0-M2.
The vault-java-driver versions 5.2.0 through 6.2.3 have a vulnerability where TLS certificate and hostname verification can be silently disabled in certain conditions, despite the caller requesting verification. This occurs when an SslConfig is passed without calling build(), restored via Java deserialization, or when the VAULT_SSL_VERIFY environment variable is set to a truthy value other than "true". This results in the driver installing a trust-all SSLContext, allowing a network attacker to intercept and read Vault tokens and secrets in transit and forge responses. The issue is fixed in version 7.0.0.
SumatraPDF versions 3.6.1 and earlier contain a vulnerability in their HTTPS update metadata and crash-symbol request handling. The HttpGet() function disables hostname verification by passing INTERNET_FLAG_IGNORE_CERT_CN_INVALID to WinINet, allowing a network attacker with a trusted certificate for a malicious domain to impersonate the update server. This can lead to injection of promotional content and attacker-controlled archives during symbol extraction. Installer replacement is prevented by other validation steps. No fix is currently available.
CVE-2026-117666 is a critical vulnerability in the deadtrickster ssl_verify_fun library that improperly validates TLS certificates with hostnames containing partial-label wildcards. This flaw allows an attacker performing a man-in-the-middle attack to impersonate a TLS peer by exploiting the wildcard matching logic that incorrectly accepts certificates for unauthorized subdomains or IP literals. The issue affects versions from 1.0.1 up to but not including 1.1.8. It is fixed in version 1.1.8.
Apache bRPC versions before 1.18.0 have an improper validation of TLS server certificates where the certificate's identity is not bound to the expected DNS name or IP address. This allows a network attacker who can intercept or redirect connections and has a valid certificate for a different name trusted by the client to impersonate the intended TLS endpoint. The issue is fixed in version 1.18.0 by enforcing hostname verification during the TLS handshake.
CVE-2026-86410 is a high-severity vulnerability in the curl command line tool where SSH host verification options are only set when interacting directly via SFTP or SCP, but not when following redirects. This improper validation of certificates with host mismatch can lead to compromised confidentiality, integrity, and availability during SSH connections.
Progress MarkLogic Server versions 11.x prior to 11.3.7 and 12.x prior to 12.1.0 have a vulnerability where TLS certificate hostnames are not consistently validated for certain outbound connections. This improper validation could allow a network-positioned attacker to intercept or modify communications with the affected service. The vulnerability is identified as CWE-297 and has a CVSS 3.1 score of 7.4, indicating high severity.
MariaDB Connector/C versions from 3.4.1 up to but not including 3.4.10 contain a vulnerability where the TLS hostname verification mismatch is not properly rejected during Zero-Configuration SSL authentication-switch logic. This flaw allows an active man-in-the-middle attacker with a valid certificate for a different hostname to request mysql_clear_password and potentially obtain the database password over the attacker-controlled TLS connection. The issue is fixed in version 3.4.10. Other MariaDB connectors are not affected.
Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift.
Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the host
name that was connected to. That comparison walks the subjectAltName dNSName entries first and consults the certificate Common Name afterwards. A name that does not match yields a "skip" result rather than
a rejection, so a certificate whose subjectAltName entries are all present and all non-matching falls through to the Common Name, which can then satisfy the check.
RFC 6125 section 6.4.4, and RFC 9525 section 2, require that the Common Name is not consulted when a dNSName subjectAltName is present. A certificate carrying subjectAltName entries for one name and a
Common Name for another is therefore accepted for a connection to the second name.
Exploitation requires an attacker positioned on the network path who holds a certificate that chains to a certificate authority in the client's trust store and whose Common Name matches the connected host
name. Public certificate authorities have not issued on Common Name alone for many years, so this is principally a concern for deployments using a private or enterprise public-key infrastructure.
This issue affects the C++ library of Apache Thrift from 0.7.0 through 0.24.0 and the D library from 0.9.0 through 0.24.0. Users should upgrade to 0.25.0.
Joyland.ai suffers from improper validation of TLS certificates, specifically failing to verify hostnames. This flaw allows a malicious host to connect or intercept chat messages by presenting a certificate with a mismatched hostname. The vulnerability affects all versions of Joyland.ai. It has a medium severity with a CVSS score of 5.3. No official patch or remediation guidance is currently available from the vendor.
CVE-2026-19553 is a vulnerability in Python's CPython ssl module where hostname verification can be silently skipped if the server_hostname argument is not provided to certain SSL APIs, despite SSLContext.check_hostname being set to True. This can cause programs to mistakenly believe hostname verification succeeded. The issue affects multiple Python versions prior to fixed releases. Mitigation involves explicitly passing a valid non-empty server_hostname value to the affected APIs. Fixed versions raise an error instead of silently skipping verification.
CVE-2026-91769 is a vulnerability in PHP's OpenSSL stream peer verification where certificate validation incorrectly accepts certificates with a host name mismatch. Specifically, if a certificate includes subjectAltName (SAN) entries, PHP improperly falls back to validating the Common Name (CN) when no SAN matches, violating RFC 6125. This flaw allows a certificate trusted for one hostname to be used to impersonate another, potentially enabling man-in-the-middle attacks. The vulnerability has a medium severity with a CVSS score of 4.3. No affected versions or patch information are explicitly provided.
CVE-2026-63374 is a critical vulnerability in the AnyIO asynchronous networking framework prior to version 4.14.2. The issue involves improper certificate validation due to the use of the outdated IDNA 2003 standard instead of IDNA 2008 when handling internationalized hostnames. This flaw allows an attacker who can hijack or redirect connections to a non-ASCII domain to present a legitimate certificate for a different ASCII hostname, causing the client to incorrectly validate the malicious endpoint's certificate. The vulnerability is fixed in AnyIO version 4.14.2.
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. From 0.25.0 until 0.27.6, the browser SSH path in warpgate-web-ssh/src/manager.rs handles RCEvent::HostKeyUnknown without the presenting hop identity and instead passes ssh_options.host and ssh_options.port for the final target to KnownHosts::trust. In Prompt and AutoAccept modes, a jump host key can therefore be stored for the target address. A machine later presenting the jump host key at the target address can be accepted as the target, allowing interception of user traffic and a newly issued certificate when certificate authentication is used. The native SSH path is unaffected because it tracks each hop separately. This issue is fixed in version 0.27.6.
PJSIP pjproject versions 2.17 and earlier have an improper certificate validation vulnerability in the OpenSSL and GnuTLS backends. The flaw involves incorrect handling of DNS SubjectAltName values containing embedded NUL bytes, allowing an attacker with a specially crafted certificate from a trusted issuer to impersonate a target server during TLS verification. This can lead to interception of SIP sessions and theft of REGISTER credentials. The mbedTLS backend is not affected. No fixed version is currently available.
Improper validation of certificate with host mismatch in the MQTT client TLS connection layer in AWS IoT Device SDK for Python 1.5.3 through 1.6.0 on Python 3.7 and later might allow an adversary-in-the-middle actor to impersonate the AWS IoT Core endpoint, read device telemetry, and inject arbitrary MQTT messages that the device processes as authentic, via a certificate issued for an unrelated hostname by a certificate authority present in the device trust store.
To remediate this issue, users should upgrade to version 1.6.1.
Apache ZooKeeper versions 3.8.0 through 3.8.6 and 3.9.0 through 3.9.5 have a vulnerability in quorum TLS where peer hostname verification is improperly enforced in FIPS-mode deployments. This allows a CA-trusted peer certificate with a Subject Alternative Name (SAN) that does not match the connected host to join quorum traffic, participate in leader election, and enter replication flows. The issue is fixed in versions 3.8.7 and 3.9.6.
Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains an Improper Validation of Certificate with Host Mismatch vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access.