Progressive Robot hMailServer 6.0.0-B1 through 6.3.7 on Windows hands OpenSSL the names of its own TLS files - the listeners' certificates, chains, private keys and Diffie-Hellman parameters, a port's client-certificate CA file (from 6.2.19), the object store's CA file (from 6.3.4) and the ACME client's keys and certificates - as Latin-1 bytes, which on code page 1252 are the code page's own for U+00A0 to U+00FF, and OpenSSL's file opening on Windows reads a name as UTF-8 first and opens the file at that reading when it is there, or creates it there when its folder is. When every byte of a configured name outside ASCII also reads as UTF-8 - for example U+00C3 U+00A9, the bytes C3 A9, which are U+00E9 in UTF-8 - the server used the file at that other name whenever one was there, which allows a local attacker who can create that file or its folder but cannot change the configured one, as any user can by default beside a file an administrator keeps under ProgramData, to have a port that logs on by client certificate (from 6.2.25) accept certificates from a certificate authority of the attacker's own and so sign in over the network as any mailbox without its password; to have the server trust such an authority for its object store and, intercepting that connection, read and modify the messages it stores; to receive the private keys the ACME client writes, the key of a certificate issued for the server's names among them; or to keep TLS ports from starting. The configuration is not the default: by default these files have names in ASCII, client certificates are off on every port, and the object store and ACME are off. The Linux builds are not affected.
Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database and TlsMode=verify-full, does not hand the database client the CA file that TlsCaFile names when the file's name contains a character outside ASCII on Linux, or above U+00FF on Windows, which allows an attacker who can intercept the connection to the database server to read and modify the traffic between hMailServer and its database, by presenting, with MariaDB Connector/C 3.4.2 to 3.4.10 as the client, a certificate from any authority, its own included, for any name, and otherwise a certificate for the database server's name issued by any certificate authority in the system's trust store. The server converted the name for the client with the C runtime's conversion in the C locale, which gives an empty string for such a name, and then set no CA file at all, without an error, while certificate verification stayed on, so the client - MariaDB Connector/C, bundled on Windows and the distribution's on Linux - verified the certificate of a database server over the network against the system's trust store instead of the configured CA; Connector/C 3.4.2 to 3.4.10 (bundled on Windows in 6.3.4 to 6.3.6) went further and, with no CA file, took a certificate within its dates whose issuer it could not find, for any name, with neither its chain nor its name checked and no password proof, when the server offered first a sign-in method that hashes the password, which an attacker in the middle chooses (MariaDB's CONC-853, fixed in Connector/C 3.4.11), and Connector/C 3.4 accepted from a MariaDB 11.4 or later server a certificate the store did not vouch for when that server proved it held the account's password; on a connection it treats as local (127.0.0.1, ::1, a Unix socket, a named pipe, and localhost on Windows), Connector/C 3.4.1 and later checked neither the certificate's issuer nor its name, so that a local attacker able to stand in for the database server could present any certificate within its dates of its own making. The settings line of hmailserver --check-database still named the configured file, and the application log said the certificate had been checked. With MariaDB Connector/C 3.4.1 to 3.4.9 as the client - bundled on Windows in 6.3.4 to 6.3.6, and the client of Linux distributions that have not patched it - the missing CA file also met the precondition of CVE-2026-107819, so that a certificate issued for any other name by a trusted authority was enough to obtain the database password. On Linux the file was found only when the server ran on glibc under a locale whose character set holds the name's characters (a UTF-8 locale, or a legacy 8-bit one the system has, in whose bytes the file is then named); with no locale, LC_ALL=C or a locale the system lacks, and on Alpine (musl), the connection failed instead. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.
CVE-2026-120808 is a critical vulnerability in MongoDB Server's macOS TLS client implementation when using the Apple SecureTransport backend. The flaw allows bypassing certificate chain-of-trust validation for outbound connections to IPv6 addresses, enabling an attacker on the network path to intercept and modify encrypted traffic by presenting a crafted self-signed certificate. This affects MongoDB versions 7.0.0 through 7.0.47, 8.0.0 through 8.0.36, 8.3.0 through 8.3.15, and 9.0.0 through 9.0.6 on macOS. Fixed versions are available.
The V programming language standard library net.http up to version 0.5.2 contains a TLS certificate validation bypass vulnerability. This flaw arises because the default configuration for SSLConnectConfig.validate and FetchConfig.validate is false, causing TLS handshakes to complete without verifying certificates in both mbedtls and OpenSSL backends. As a result, attackers can intercept or modify HTTPS traffic by presenting invalid certificates such as expired, self-signed, wrong-hostname, or untrusted-root certificates unless the validate option is explicitly set to true.
The LaserGest mobile application disables TLS certificate and hostname verification via setServerTrustMode("nocheck"), allowing a man-in-the-middle attacker to intercept or modify network traffic, including credentials and API communications.
This report summarizes every TLS certificate authority (CA) incident recorded in Mozilla's CA program from 2017 through November 2026, totaling 1,581 incidents across 108 CAs. The dataset highlights incident counts, self-reporting rates, late revocations, and slow response metrics per CA. While 2026 is the busiest year with 338 incidents, only 11 incidents are classified as critical, with eMudhra's computable keys incident being the sole case where a CA lost control of its own keys. The report provides comparative incident rates normalized by peak certificate issuance per CA, revealing significant variance in incident frequency and response quality among CAs. Some CAs have been distrusted due to their incident records. This dataset is intended for transparency and analysis of CA operational security over time.
The MatchPoint Android app improperly validates TLS certificates due to a TrustManager that accepts any certificate and a permissive hostname validator. The app also permits unencrypted HTTP traffic. This misconfiguration allows an attacker who can intercept network traffic to read and modify communications, including sensitive credentials and personal data.
CVE-2026-96453 is a vulnerability in the Red Hat build of Keycloak 26.4's Admin CLI tool (kcadm). When administrators use a custom truststore to verify the Keycloak server's identity, the tool improperly accepts any self-signed certificate if the hostname matches. This flaw enables a network attacker positioned to intercept traffic to impersonate the server, steal administrative credentials, and perform unauthorized management actions.
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.
The VitaFit Android application versions before 2.8.1.0 contain a vulnerability in TLS/SSL certificate validation due to a custom X509TrustManager that trusts all certificates and a hostname verifier that accepts any hostname. This flaw enables network-based attackers to perform man-in-the-middle attacks, intercepting and modifying HTTPS traffic. Exploitation can lead to capturing account sessions and health-related API data, and attackers may delete authentication records to block legitimate logins. The issue is fixed in version 2.8.1.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-19534 is a security vulnerability related to the Red Hat Trusted Artifact Signer (RHTAS) Operator used with OpenShift Container Platform versions 4.17 through 5.0. The vulnerability involves a flaw in the undici HTTP client library where custom TLS certificate validation functions are discarded during internal configuration, potentially allowing attackers to bypass custom cryptographic protections such as certificate or public-key pinning. This could enable interception or modification of encrypted communications if an attacker is positioned on the network. The vulnerability does not affect standard system trust stores or default certificate validations, limiting exposure to environments using specialized certificate validation handlers. Red Hat has released RHTAS version 1.5.1, but no explicit fix addressing this vulnerability is mentioned in the advisory. No known exploits are reported in the wild.
CVE-2026-115731 is a critical vulnerability in Perforce Puppet Enterprise involving deserialization of untrusted data in the report-processing code. An attacker with any CA-signed agent certificate can execute arbitrary code on the Puppet Server by submitting a crafted report. If the certificate authority autosigns requests without strong verification, unauthenticated network attackers may obtain such certificates and exploit this flaw. The vulnerability affects multiple versions of Puppet Enterprise released between 2023 and 2026.
An improper certificate validation vulnerability (CWE-295) exists in the operating system certificate bundle included in various Elastic products' Docker images and components. The bundle contains root CAs that trust eight eMudhra intermediate CAs whose private keys have been compromised. An attacker with network access between the product and a remote party could use these compromised keys to issue fraudulent certificates, enabling interception or modification of TLS-protected traffic.
Nanosystems Supremo for Windows and macOS before 5.0.2.3874 contains an improper certificate validation vulnerability that allows adjacent attackers to intercept TLS connections by presenting untrusted certificates. Attackers on the same network can terminate and relay the client's TLS session using self-signed certificates to read usernames, SHA-256 password hashes, and license codes.