CVE-2026-126621: Progressive Robot hMailServer · Improper Certificate Validation
Affects Progressive Robot hMailServerSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 11 Nov 2026, 08:50 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Progressive Robot LtdhMailServer | Affected
| Fixed in– |
AI-suggested
Mitigation involves ensuring default configurations are used: keep TLS-related file names strictly ASCII, disable client certificate authentication on ports, and disable the object store and ACME client features if not needed. Restrict local file creation permissions to trusted administrators to prevent attackers from placing malicious files. Monitor vendor advisories for official fixes or updates.
Description
CVE-2026-126621 is a high-severity vulnerability in Progressive Robot Ltd's hMailServer versions 6.0.0-B1 through 6.3.7 on Windows. It involves improper certificate validation due to how OpenSSL handles TLS file names encoded as Latin-1 bytes versus UTF-8. This discrepancy allows a local attacker with file creation privileges to substitute certificate files, enabling unauthorized client certificate authentication, interception and modification of stored messages, access to private keys used by the ACME client, or denial of TLS port startup. The vulnerability requires non-default configurations with non-ASCII file names and enabled client certificates or object store/ACME features. Linux builds are not affected.