Skip to main content
VulnerabilityPublished

CVE-2026-126609: Progressive Robot hMailServer · Improper Certificate Validation

Affects Progressive Robot hMailServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 6.3.7 : patch Progressive Robot hMailServer soon.

Data as of 11 Nov 2026, 08:50 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.17.5
Patch
Available – fixed in 6.3.7
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Progressive Robot LtdhMailServerAffected
  • >=6.2.25 <=6.3.7
Fixed in–

AI-suggested

A fix is available in versions after 6.3.7 (implied by affected versions ending at 6.3.7). Users should upgrade hMailServer to a version later than 6.3.7 once released. Until then, avoid configurations that specify a root certificate file with PostgreSQLSslRootCert or TlsCaFile on affected versions. Restrict local file creation permissions in directories adjacent to the configured certificate file and system drive root to prevent attacker file placement. Verify the client library in use; the bundled MariaDB Connector/C is not affected. Monitor vendor advisories for official patches and updates.

Description

hMailServer versions 6.2.25 through 6.3.7 on Windows with PostgreSQL configured to require SSL certificate validation may improperly validate the root certificate file due to encoding mismatches. This allows a local attacker who can place a specially named file in certain directories to cause hMailServer to trust a malicious certificate authority, enabling interception and modification of database traffic including credentials. The issue affects configurations using PostgreSQLSslRootCert or TlsCaFile with certain client libraries. Linux builds and default configurations without a root certificate file named are not affected.

References

Community reviews

Loading reviews…