CVE-2026-126626: fallo de gravedad media en Progressive Robot Ltd hMailServer
Overly Restrictive Account Lockout Mechanism in hMailServer
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 5.3epss 0.5%
The web services listener of Progressive Robot hMailServer 6.3.3 through 6.3.7 counts every failed CardDAV, CalDAV or Autodiscover sign-in from a proxy it trusts - one on the same machine, or one named in WebServicesTrustedProxies, whose X-Forwarded-Proto it believes - against the proxy's own address, which allows a remote unauthenticated attacker who can reach the proxy to have that address banned from the server's mail listeners. The listener, off by default (WebServicesHttpPort and WebServicesHttpsPort 0), signs an account in with HTTP Basic over HTTPS for CardDAV from 6.3.3 and for CalDAV and Outlook Autodiscover from 6.3.4. Behind a TLS-terminating proxy, which the server trusts when it is on the same machine or named in WebServicesTrustedProxies, the listener takes the client's HTTPS from the proxy's X-Forwarded-Proto header, but it does not believe X-Forwarded-For and sees the proxy's address for every client. Each failed sign-in counted towards the auto-ban against that address, so that failed sign-ins through the proxy from anybody, under any user name, reaching MaxInvalidLogonAttempts (3 within 30 minutes by default) wrote an IP range that refused the proxy's address at the SMTP, POP3, IMAP and ManageSieve listeners for AutoBanMinutes (60 by default), and could write it again each time it lapsed. For a proxy on the same machine that address is the loopback address, so that a webmail on that machine, local scripts that submit mail and the other local clients of the mail listeners were shut out; for a proxy at another address that also carries mail, every mail client behind it was. Such a proxy forwarding to the listener's HTTPS port, re-encrypting, was counted against in the same way, and listing it in WebServicesTrustedProxies did not spare it. The auto-ban is on by default and AutoBanNeverBan, which spares an address, is empty by default; the listener itself went on serving the proxy.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Productos afectados
Progressive Robot Ltd · hMailServerCVEs relacionadas — Progressive Robot Ltd hMailServer
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-100741CRITICALImproper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in hMailServerEPSS 1.7%CVE-2026-126623HIGHInefficient Algorithmic Complexity in hMailServerEPSS 0.6%CVE-2026-126613HIGHAllocation of Resources Without Limits or Throttling in hMailServerEPSS 0.5%CVE-2026-107585MEDIUMAllocation of Resources Without Limits or Throttling in hMailServerEPSS 0.4%CVE-2026-126618MEDIUMImproper Restriction of Excessive Authentication Attempts in hMailServerEPSS 0.4%CVE-2026-126614MEDIUMImproper Restriction of Excessive Authentication Attempts in hMailServerEPSS 0.4%