CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVE-2026-126612 Improper Link Resolution Before File Access ('Link Following') in hMailServer
High (7.8) in progressive robot ltd hmailserver. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-59 Improper Link Resolution Before File Access (Link Following)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitLab (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126612 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126612?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126612?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126612 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126612)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126612"><img src="https://cve.bz/cve/badge/CVE-2026-126612.svg" alt="CVE-2026-126612"></a>
Affected
- progressive robot ltd:hmailserver
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Progressive Robot Ltd hMailServer | from 6.0.0 through 6.3.7 |
Attack patterns (CAPEC)
- CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
- CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.