# CVE-2026-126625: Incorrect Default Permissions in hMailServer

> Local users can plant programs in a writable install folder that the hMailServer installer runs as the installing administrator.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/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:** Yes
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-q63q-8h8v-j42v

## What is CVE-2026-126625?

CVE-2026-126625 is a medium-severity insecure configuration 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

Incorrect default permissions in the Windows installer of Progressive Robot hMailServer 6.3.7 allow a local authenticated user to run code as the administrator who installs the product, when it is installed into a new program folder in a location whose permissions let every user write, such as 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 its setup lets Inno Setup make a new program folder first, with the permissions the folder above hands down, and replaces them only afterwards, tens of milliseconds later (33 to 139 milliseconds in the project's test runs). In that time any local account may make files and folders in the new folder, which keep that account as their owner, among them the Bin folder that setup then copies the programs into. Setup runs programs from Bin with the administrator's elevated rights, registering the service among them, before its hardening at the end of setup takes such a folder back, and those programs load a library placed in Bin in place of the system's. The default installation under Program Files, whose folders give ordinary users read and execute only, is not affected.

Weakness: CWE-276 (Incorrect Default Permissions)

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

Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.


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

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

## Is CVE-2026-126625 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126625 is a medium-severity insecure configuration 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-126625 in the wild and no public exploit code.
Exposure: Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.

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-126625/ (Markdown: https://insights.sbomify.com/CVE-2026-126625/index.md)
```

## Sources

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

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