PT-2026-145078
CVE-2026-126621
·
Published
2026-11-11
·
Updated
2026-11-11
Description by
CVSS 3.1
7.5
HighMetricsAV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions
hMailServer versions 6.0.0-B1 through 6.3.7
Description
On Windows, the software passes TLS file names—including listener certificates, chains, private keys, Diffie-Hellman parameters, client-certificate CA files, object store CA files, and ACME client keys—to OpenSSL as Latin-1 bytes. Because OpenSSL on Windows attempts to read file names as UTF-8 first, a discrepancy occurs when configured names contain non-ASCII characters. A local attacker who can create files or folders in the same directory as the configured files (such as under ProgramData) can trick the server into using a malicious file instead of the intended one. This can lead to several critical outcomes: allowing unauthorized network sign-ins as any mailbox by using a rogue certificate authority, enabling the interception and modification of messages in the object store, allowing the attacker to obtain private keys written by the ACME client, or preventing TLS ports from starting. This issue requires a non-default configuration where non-ASCII characters are used in file names or specific features like client certificates, object store, or ACME are enabled.
Recommendations
For hMailServer versions 6.0.0-B1 through 6.3.7, ensure that all TLS-related file names use only ASCII characters to prevent the server from misinterpreting the file paths.
Restrict write access to the directories where TLS certificates, private keys, and CA files are stored to prevent local users from creating malicious files.
Disable the use of client certificates on ports, the object store, and the ACME client if these features are not strictly required.
Found an issue in the description? Have something to add? Feel free to write us 👾