CVE-2026-126616
Received Received - Intake

Auto-ban Bypass via UTF-8 Character in hMailServer

Vulnerability report for CVE-2026-126616, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-11

Last updated on: 2026-11-11

Assigner: GitLab Inc.

Description

The auto-ban of Progressive Robot hMailServer 6.2.0 through 6.3.3, with a MySQL or MariaDB database, can be kept from banning an address after repeated failed logons, which allows a remote unauthenticated attacker to go on guessing account passwords from a single address without being banned. The server makes its MySQL tables in MySQL's utf8 character set, which holds no character outside the Basic Multilingual Plane, sends its statements as UTF-8 over a utf8mb4 connection and leaves the database's default strict mode in place. From 6.2.0 it decodes the user name of a SASL PLAIN logon as UTF-8, so the name can hold such a character. When the failed logons counted from one address reach MaxInvalidLogonAttempts (3 by default), the server clears that address's count, saves an IP range named "Auto-ban: " followed by the user name of the logon that reached the limit, and drops the connection. If such a character is in the part of the user name that the range's name keeps (the name is cut to 100 characters), the database refuses the range: no range is saved, the address is not refused, and, its count having already been cleared, it is given the next full set of attempts. An attacker can in this way spend all but the last attempt of each set on password guesses, and make the last under such a name. On Windows, POP3 AUTH PLAIN reaches it on a server as installed, and IMAP AUTHENTICATE PLAIN where IMAP SASL authentication is turned on (off by default); on Windows and on Linux (from 6.3.0), SMTP AUTH PLAIN reaches it where plain-text authentication is allowed (off by default), and ManageSieve and CardDAV where they are turned on (off by default). Each failed save is reported in the server's error log. A database whose strict mode has been turned off stores the character as a question mark and makes the first such ban, but refuses every later ban named after the same user name, or after one holding other such characters in their place, as a duplicate while the first stands, since the server cannot look up a name holding such a character there.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-11
Last Modified
2026-11-11
Generated
2026-11-11
AI Q&A
2026-11-11
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Progressive Robot Ltd hMailServer From 6.2.0 (inc) to 6.3.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-307 The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects hMailServer versions 6.2.0 through 6.3.3 when using MySQL or MariaDB databases. It allows attackers to bypass auto-ban restrictions by using usernames containing characters outside the Basic Multilingual Plane (BMP). The database rejects the auto-ban IP range creation due to a string value or collation mismatch, preventing the address from being banned. This lets attackers repeatedly attempt password guesses without being locked out.

Detection Guidance

Check hMailServer logs for repeated failed logon attempts from the same IP address without corresponding auto-ban entries. Look for error messages indicating failed INSERT operations on the hm_securityranges table due to string value or collation issues.

Impact Analysis

An attacker can exploit this to perform brute-force password guessing attacks against your hMailServer without being blocked. This increases the risk of unauthorized account access. The vulnerability affects POP3, IMAP, and SMTP authentication depending on your server configuration. Failed attempts are logged but do not trigger bans.

Mitigation Strategies
  • Upgrade hMailServer to version 6.3.4 or later to fix the utf8mb4 encoding issue.
  • Manually alter the hm_securityranges table to use utf8mb4 encoding if upgrading is not immediately possible.
  • Disable plain-text authentication methods (POP3 AUTH PLAIN, IMAP AUTHENTICATE PLAIN, SMTP AUTH PLAIN) if not required.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-126616. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...