CVE-2026-104659: Progressive Robot hMailServer · Origin Validation Error
Affects Progressive Robot hMailServerSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 6.3.6 soon.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% 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:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 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 21 Nov 2026.
What to do
Upgrade hMailServer and hmailserver/hmailserver to 6.3.6.
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
If you cannot patch yet, administrators should ensure the REST API listener is disabled if not needed, restrict access to the loopback interface, and monitor for suspicious activity. Because the listener is off by default, avoid enabling it unless necessary and consider additional network-level protections against DNS rebinding attacks.
Description
Missing Host header validation and missing throttling of failed administrator sign-ins in the REST API listener of Progressive Robot hMailServer 6.0.0 through 6.3.5 allow a remote attacker to brute-force the server administrator's password through the administrator's own browser by DNS rebinding. The listener, which is off by default and bound to the loopback when enabled, answered requests whatever their Host header named, and a failed sign-in with the administrator's password from the loopback was neither auto-banned nor delayed. A web page whose host name the attacker rebinds to 127.0.0.1, opened in a browser on the server, can therefore send authenticated requests to the listener, read the answers and try administrator passwords at full speed until one is accepted, giving the attacker full administrative control of the mail server.