CVE-2026-126612 · Package
NO FIX YET · SEE WHAT TO DO
The Windows installer for hMailServer 6.0.0 through 6.3.7 follows junctions, symbolic links or mount points in the program folder path without checking who controls them. A local authenticated user can redirect installed programs into a folder they control, so the mail server service (LocalSystem or its virtual account) and programs administrators run from Bin execute attacker code.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems running hMailServer 6.0.0 through 6.3.7 on Windows where the install path passes through a link or a renameable folder, typically a non-default install location. The default Program Files installation is stated not to be affected, and the sources say the 6.3.7 hardening does not cover this path. Attacker needs a local account on the machine.
Not affected if default-config, program-files-install
Who cares hmailserver, mail-server, windows
6.3.7 and the affected range 6.0.0 through 6.3.7.dir /AL or fsutil reparsepoint query, and whether non-admin users can rename parent folders.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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
6.3.7 or later is referenced as the earlier fix for CVE-2026-107571, which the sources say does not cover this issue; no fixed version for this CVE is stated in the sources.NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.