# CVE-2026-126612: Improper Link Resolution Before File Access ('Link Following') in hMailServer

> Local users can plant junctions so the hMailServer Windows installer runs code as the service account or administrator.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/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:** Local or same network only
- **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-hvr4-pggg-cr56

## What is CVE-2026-126612?

CVE-2026-126612 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, with no action from the victim.

### Official description

Improper link resolution in the Windows installer of Progressive Robot hMailServer 6.0.0 through 6.3.7 allows a local authenticated user to run code as the mail server's service account or as an administrator when the path to the program folder passes through a junction, a symbolic link or a mount point that the user controls or that every user may change, such as a junction made at the root of a drive, which takes the root's permissions, or through a folder that every user may rename. Setup installed the programs through any such link without first checking who controls it, or whether a folder above the program folder may be renamed, and the service is registered to run the programs by that path, so the programs are installed where a link another account controls leads, or that account can later make the path lead to a folder it controls; the service, which runs as LocalSystem or as its virtual account, and the programs administrators run from Bin are then started from there. 6.3.7's fix for CVE-2026-107571 does not cover this: its hardening of the program folder, Bin and ControlPanel does not change a folder reached through a link that the administrators do not alone control, and setup does not refuse such a path: it installs through the link and at most reports afterwards that the folders could not be hardened. The default installation under Program Files is not affected.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

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


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

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

## Is CVE-2026-126612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126612 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, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126612 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-126612/ (Markdown: https://insights.sbomify.com/CVE-2026-126612/index.md)
```

## Sources

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

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