Progressive Robot hMailServer 6.2.25 through 6.3.7 on Windows, with a PostgreSQL database, the connection's sslmode
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 11 Nov 2026, 10:05 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– |
GitHubhmailserver/hmailserverpkg:github/hmailserver/hmailserverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability depends on non-default SSL configurations specifying a root certificate file, administrators should verify their hMailServer SSL settings and avoid configurations that specify root certificate files with names that could be interpreted differently due to encoding mismatches. Using the bundled MariaDB Connector/C instead of Oracle MySQL client libraries on affected versions can avoid the issue. Restricting local file creation permissions in the relevant directories can also mitigate the risk. Monitor vendor advisories for any official fixes or updates.
Description
A vulnerability in Progressive Robot hMailServer versions 6.2.25 through 6.3.7 on Windows affects configurations using a PostgreSQL database with certain SSL modes and root certificate file settings. The issue arises from how the root certificate file name is handled with Windows code pages and UTF-8 encoding, allowing a local attacker to cause hMailServer to trust a malicious certificate authority. This enables interception and modification of database traffic, including the database password. The vulnerability does not affect default configurations and is specific to Windows builds with PostgreSQL or Oracle MySQL client libraries replacing the bundled MariaDB Connector/C.