Skip to main content
VulnerabilityPublished

CVE-2026-104704: Progressive Robot hMailServer · Cleartext Transmission

Affects Progressive Robot hMailServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 6.3.6 soon.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.3.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 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 21 Nov 2026.

What to do

Upgrade hMailServer and hmailserver/hmailserver to 6.3.6.

Affected software

ProductAffectedFixed in
Progressive Robot LtdhMailServerAffected
  • >=6.0.0 <6.3.6
Fixed in
  • 6.3.6
GitHubhmailserver/hmailserverpkg:github/hmailserver/hmailserverOther threatsAffected
  • >=6.0.0 <6.3.6
Fixed in
  • 6.3.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, administrators should consider alternative mitigations such as enforcing strict TLS policies manually or using external mail gateways that enforce proper DANE validation. Monitoring for updates from Progressive Robot Ltd is recommended.

Description

Progressive Robot hMailServer 6.0.0 through 6.3.5 does not enforce TLS for outbound SMTP delivery to a mail exchanger whose DNSSEC-validated TLSA records contain no DANE-EE (usage 3) record, contrary to RFC 7672 section 2.2. The server used only DANE-EE records and treated a validated TLSA record set consisting of DANE-TA (usage 2) or otherwise unusable records as if no records were published, so delivery to such a host fell back to opportunistic TLS. An attacker with an active position on the network path between the server and the recipient's mail exchanger can suppress or break the STARTTLS negotiation and cause messages to be delivered in cleartext, where they can be read and modified.

References

Community reviews

Loading reviews…