Is CVE-2026-126618 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-126618 being exploited in the wild.

How severe is CVE-2026-126618?

Medium severity, with a CVSS score of 5.3, published 11 November 2026.

Which products and versions are affected?

Progressive Robot hMailServer 6.0.0-B1 through 6.3.7.

How is CVE-2026-126618 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-126618?

Check whether you run Progressive Robot hMailServer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-126618: hMailServer account password brute-force via auto-ban bypass

CVE-2026-126618 · Severity: medium · CVSS 5.3 · Published 2026-11-11

hMailServer, an email server, implements automatic IP banning after repeated failed login attempts to prevent password guessing attacks. An attacker can bypass this protection by crafting usernames with specific properties (length, special characters, or non-ASCII bytes) that cause the ban system to fail silently, allowing unlimited password guesses across multiple IP addresses on SMTP, IMAP, POP3, and web service protocols.

Technologies: Progressive Robot hMailServer. Vendors: Progressive Robot.

Quick answers

Is CVE-2026-126618 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-126618 being exploited in the wild.
How severe is CVE-2026-126618?: Medium severity, with a CVSS score of 5.3, published 11 November 2026.
Which products and versions are affected?: Progressive Robot hMailServer 6.0.0-B1 through 6.3.7.
Is there a fix for CVE-2026-126618?: No fixed version is recorded yet. Restrict SMTP, IMAP, POP3, and web service authentication to trusted networks or require additional authentication factors (e.g., multi-factor authentication) to reduce exposure to brute-force attacks while a patch is applied. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-126618 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-126618?: Check whether you run Progressive Robot hMailServer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Restrict SMTP, IMAP, POP3, and web service authentication to trusted networks or require additional authentication factors (e.g., multi-factor authentication) to reduce exposure to brute-force attacks while a patch is applied.

Technical details

The vulnerability stems from a flaw in the auto-ban mechanism's IP range naming logic: when a username exceeds 90 characters or contains NUL bytes, the database insertion of the auto-ban IP range fails (due to truncation or statement parsing), leaving the attacker's address unbanned and its failed-attempt counter reset. An unauthenticated remote attacker on the SMTP, IMAP, POP3, ManageSieve, CalDAV/CardDAV, or REST API ports can trigger this by cycling through password guesses under maliciously-crafted usernames, receiving a fresh set of attempts after each ban-system failure. The impact scales with the number of available IP addresses the attacker can use.

Affected products

Progressive Robot hMailServer 6.0.0-B1 through 6.3.7

Timeline

2026-11-11: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.