Incorrect Default Permissions in hMailServer
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:HSeverity
medium6.7CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Source guidance available
Review the recorded instructions. Guidance may be a workaround rather than a fixed version.
What this means
hMailServer 6.3.7 has incorrect default permissions, allowing a local authenticated user to run code as the administrator who installs the product, if installed in a location with weak permissions. The vulnerability occurs when the setup creates a new program folder with inherited permissions. The default installation under Program Files is not affected.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Attack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Progressive Robot Ltd · GitLab
hMailServer
1 range
Progressive Robot Ltd · GitLab
hMailServer
Compare with this publisher’s ranges. This does not inspect your installation.
affected
6.3.7
Other versions: unaffected
What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
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.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher 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.
References
3 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-126625View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.