# CVE-2026-126624: Unverified Ownership in hMailServer

> Local users can plant files in a pre-created program folder so hMailServer setup runs code as the mail service or administrator.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **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-5vrf-r3xw-59r9

## What is CVE-2026-126624?

CVE-2026-126624 is a high-severity privilege escalation vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Unverified ownership in the Windows installer of Progressive Robot hMailServer 6.3.7 allows a local authenticated user to run code as the mail server's service account or as an administrator when setup installs into, or upgrades, a program folder that accounts other than the administrators could write before, such as one made beforehand at the root of a drive. 6.3.7 fixed CVE-2026-107571 by giving the program folder, Bin and ControlPanel permissions that only administrators may change, but setup refused nothing that was already in them, or in the folders that hold the event script, the add-ons and the database scripts: a program, a library, a script or a settings file that another account owns, or whose own permissions let another account change it, is kept with that owner and those permissions, which the hardening of the folders does not take away. Setup then runs programs from Bin with the administrator's elevated rights, and the service, which runs as LocalSystem or as its virtual account, runs them and the event script, so that a library such an account placed in Bin is loaded in place of the system's; the account can still change the file after the installation. The default installation under Program Files is not affected.

Weakness: CWE-283 (Unverified Ownership)

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

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


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

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

## Is CVE-2026-126624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126624 is a high-severity privilege escalation vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-126624 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-126624/ (Markdown: https://insights.sbomify.com/CVE-2026-126624/index.md)
```

## Sources

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

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