# CVE-2026-126621: Improper Certificate Validation in hMailServer

> Local attackers can make hMailServer on Windows accept attacker certificates, read and modify stored mail, or steal server keys when certain non-ASCII certificate names are configured.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-2q54-5c4c-vg9w

## What is CVE-2026-126621?

CVE-2026-126621 is a high-severity security feature bypass vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Progressive Robot hMailServer 6.0.0-B1 through 6.3.7 on Windows hands OpenSSL the names of its own TLS files - the listeners' certificates, chains, private keys and Diffie-Hellman parameters, a port's client-certificate CA file (from 6.2.19), the object store's CA file (from 6.3.4) and the ACME client's keys and certificates - as Latin-1 bytes, which on code page 1252 are the code page's own for U+00A0 to U+00FF, and OpenSSL's file opening on Windows reads a name as UTF-8 first and opens the file at that reading when it is there, or creates it there when its folder is. When every byte of a configured name outside ASCII also reads as UTF-8 - for example U+00C3 U+00A9, the bytes C3 A9, which are U+00E9 in UTF-8 - the server used the file at that other name whenever one was there, which allows a local attacker who can create that file or its folder but cannot change the configured one, as any user can by default beside a file an administrator keeps under ProgramData, to have a port that logs on by client certificate (from 6.2.25) accept certificates from a certificate authority of the attacker's own and so sign in over the network as any mailbox without its password; to have the server trust such an authority for its object store and, intercepting that connection, read and modify the messages it stores; to receive the private keys the ACME client writes, the key of a certificate issued for the server's names among them; or to keep TLS ports from starting. The configuration is not the default: by default these files have names in ASCII, client certificates are off on every port, and the object store and ACME are off. The Linux builds are not affected.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-126621?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-126621?

No fix has been published for CVE-2026-126621 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126621 being exploited?

There is no known exploitation of CVE-2026-126621 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126621 and fix it if it is affected.

What it is: CVE-2026-126621 is a high-severity security feature bypass vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126621 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: Progressive Robot Ltd hMailServer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126621/ (Markdown: https://insights.sbomify.com/CVE-2026-126621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126621
- OSV: https://osv.dev/vulnerability/CVE-2026-126621

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126621/
Summaries are generated and may contain mistakes; the official description above is the record.
