CVE-2026-126625
Incorrect Default Permissions in hMailServer
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.
Fixes and workarounds
Fix
Upgrade to hMailServer 6.3.8, whose setup makes a new program folder, every folder above it that is not there, and Bin and ControlPanel in it, with permissions of their own from the moment each exists - SYSTEM and the Administrators full control, Users read and execute, nothing inherited, the Administrators the owner - before Inno Setup makes a folder or copies a file, each made by its name relative to the folder above it, which setup holds open. Until then, install hMailServer under Program Files, or into a new folder inside a folder that only administrators may change. To install elsewhere, first make the program folder from an elevated Command Prompt and give it a protected set of permissions - icacls "<program folder>" /inheritance:r /grant:r *S-1-5-18:(OI)(CI)F *S-1-5-32-544:(OI)(CI)F *S-1-5-32-545:(OI)(CI)RX, then icacls "<program folder>" /setowner *S-1-5-32-544 - check with dir /q /a "<program folder>" that nothing has been made in it, and restart Windows before running setup, so that nothing opened in it before its permissions were set stays open.
Source: CNA: GitLabAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| hMailServer Progressive Robot Ltd |
6.3.7 (affected)
Other versions: unaffected |
CNA: GitLab |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 6.7 medium |
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | CNA: GitLab |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.