CVE-2026-126615

The sign-in of Progressive Robot hMailServer 6.2.22-pre2 through 6.3.7 takes for an account names that are not its address but under which the database's own comparison finds it, while the per-name lockout and the compromised-account hold are kept by the name as the client gave it. This allows a remote unauthenticated attacker to go on guessing an account's password beyond the lockout's threshold, and anyone who has the password of an account held for review to sign in to it. The per-name lockout (from 6.2.22-pre2; AccountLockoutThreshold in hMailServer.ini, 0, off, by default) locks a name after repeated failed sign-ins. The hold (from 6.3.4, where the compromised-account detection is set to enforce, which is not the default) refuses an account judged to have been taken over. Both are asked, before the password, of the name the client gave: trimmed, in lower case and with a domain alias or the default domain applied. The account whose password the sign-in then checks is whichever one the database finds under that name. The databases find an account under spellings that this key counts apart. MySQL and MariaDB find it under one with accented letters in place of plain ones, and MariaDB 11.8, in a database made before 6.3.4, also under one with full-width letters, with a single letter in place of a pair of plain ones, or with characters its comparison ignores in any number. SQL Server and SQL Server Compact find it under one with full-width letters or with characters their comparison ignores in any number, and SQL Server also under one with a single letter in place of a pair of plain ones, with a character of Latin-1 in place of a digit and, for an address holding letters of Latin-1 outside ASCII, under those letters in the other case, and, under an accent-insensitive collation, with accented letters. PostgreSQL finds it under one holding a letter whose lower case under the database's locale is a plain letter, and, for an address holding letters outside ASCII, under those letters in the other case; on the build for musl (from 6.3.6) the server's own lower case folds nearly all of these too. On every database, a domain alias saved with white space at the end of its name gives such a spelling too, and on every database but PostgreSQL so does an account's bare local part where the default domain was saved with spaces at its end and no other white space (neither is the default). Each such spelling has a lockout threshold of its own, so the lockout limits the guesses at an account only to its threshold times the number of the account's spellings. That is far beyond any threshold for most addresses on MySQL and MariaDB, and without limit on SQL Server, on SQL Server Compact, the database the Windows installer uses by default, and before 6.3.4 on MariaDB 11.8. A locked name is got round under another spelling. A held account is signed in to under another spelling with its password over IMAP, POP3 and SMTP AUTH, and, where they are turned on (off by default), over ManageSieve, the REST API and the webmail. IMAP LOGIN, offered as installed, carries such spellings on MySQL, MariaDB and SQL Server Compact, and, on SQL Server and PostgreSQL, for some addresses; the sign-ins that carry a name as UTF-8 carry them for the others on SQL Server, and on PostgreSQL for those holding one of the plain letters another letter lowers to or a letter outside ASCII with another case. The same lookup mapped to accounts the names given by an OAuth 2.0 token, a client certificate, a Kerberos ticket and an OpenID Connect or SAML identity provider, where those are set up (none is by default), so that a name an issuer gave to one party could sign in to another's account; OAuth 2.0 tokens were mapped so from 6.2.0, before the per-name lockout existed. A name holding a NUL character, carried from 6.3.0 on Linux and 6.3.3 on Windows, failed the statement on MySQL, MariaDB and PostgreSQL.

Score
CVSS 3.1 5.3 Medium
Status
Deferred - cve@gitlab.com
Published
2026-11-11
Last modified
2026-11-17
Weaknesses
CWE-289

Affected products

References


Your early warning system for new security vulnerabilities


Open BETA

Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?

Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?

As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.

100+ new CVEs per day

Most CVEs are irrelevant to your infrastructure

Time-to-exploit < 5 days

Attackers are exploiting vulnerabilities faster than ever before

Manual research is time-consuming

Vendor websites, RSS feeds, and blogs need to be searched daily

Vulnerability scanners are lagging behind

Plugin development isn't progressing fast enough to identify risks in a timely manner

CVE Alarm provides you with immediate notifications of relevant security vulnerabilities

CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.

Real-time notification

Direct email notification without delay

Product-based filters

Only CVEs that actually affect your infrastructure

Custom criteria

Filter by CVSS-Score, exposure, products, and vendors

Team-oriented & multi-tenant capable

Assign products or alerts to specific teams or customers

More time to act

Administrators can review and install updates faster

Time savings

No more manually reviewing the flood of new CVE information

Three steps for better patch planning

With CVE Alarm you will easily receive relevant security alerts for your infrastructure.

Subscribe To
Products

Select the IT products you use. From Apache to VMware – all critical assets are monitored.

Define
Criteria

Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.

Get
Notified

Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.

Be faster
than the attackers

With CVE information, you have more time for patch planning and can close security gaps before they are exploited.

Designed for the target group companies and service providers

Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.

Companies with their own IT infrastructure

Medium-sized to large companies that need to proactively monitor their vulnerabilities

Administrators

IT professionals responsible for infrastructure security and maintenance

Security teams and cybersecurity experts

Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures

Chief Information Security Officers (CISOs) & IT managers

Decision-makers who need an overview of critical vulnerabilities

Security service providers

Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs

From experience to innovation. About us and CVE Alarm.

CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.

AVABIS GmbH – Who are we?
We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.

CVE Alarm – How did the idea come about?
In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.

This made us realize that the real problem is not a lack of information, but rather an overabundance of it.

This led to the idea of ​​developing a product that enables companies to manage this information overload and maintain control over their IT security.

Developed and operated in Germany
Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.

Get in contact with our team

Do you have questions about CVE Alarm or would you like a personal consultation?
We're happy to help.

Please use our contact form.