CVE-2026-126611 Improper Certificate Validation in hMailServer
A local attacker impersonating the database server can capture hMailServer database credentials and read or modify traffic when full TLS certificate verification is used.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-126611?
CVE-2026-126611 is a high-severity security feature bypass vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database, TlsMode=verify-full and no TlsCaFile, does not verify the database server's certificate's issuer or name when the connection is one that MariaDB Connector/C treats as local - Server= set to 127.0.0.1, ::1 or localhost (on Linux a Unix socket), to . on Windows (a named pipe), or to a comma-separated list of servers that holds such an element - which allows a local attacker who can stand in for the database server, for example by listening on its port while it is stopped or restarting, to receive the database sign-in, the password included, and to read and modify the traffic between hMailServer and its database. hMailServer applied verify-full by turning the client's certificate verification on without a CA file, but MariaDB Connector/C 3.4.1 and later, on a connection they treat as local and with no CA file, accept any certificate within its validity period that is self-signed or sent with its own root, for any name (Connector/C 3.4.2 to 3.4.10 also one whose issuer they cannot find), so the client accepted the certificate an impostor made, asked no proof of the password and allowed a switch to an authentication method that sends the password unhashed, while hmailserver --check-database said the certificate had been checked against the system's trust store and the application log that it had been checked. The Windows builds bundle Connector/C 3.4.9 (6.3.4 to 6.3.6) and 3.4.11 (6.3.7); on Linux the distribution's client is used, and Connector/C 3.3 and 3.4.0 and Oracle's MySQL client are not affected. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.
Weakness: CWE-295
Which versions are affected by CVE-2026-126611?
Only installations with a non-default setting turned on are exposed.
How do I fix CVE-2026-126611?
No fix has been published for CVE-2026-126611 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version, and do not rely on a single control for protection. More about Security feature bypass.
Is CVE-2026-126611 being exploited?
There is no known exploitation of CVE-2026-126611 in the wild and no public exploit code.
Sources
Also known as GHSA-pm2h-xjj9-fw84.