Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocal authenticated access to host
-
DeliveryLocate hMailServer installed at writable drive-root path
-
ExploitReplace service binary or plant malicious DLL in Bin
-
ExecutionService or elevated admin tool loads attacker code
-
ImpactCode execution as LocalSystem / virtual account
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires BOTH: (1) a local, authenticated non-administrator account on the host, and (2) hMailServer installed to a non-default location whose permissions are inherited from a writable parent - specifically the root of an NTFS drive, where Authenticated Users receive Modify (Windows client) or Users receive create-files/folders rights (Windows Server) over the program folder and Bin. The default Program Files installation is explicitly NOT affected because ordinary users receive only read/execute there. The concrete attack primitives are: replacing the service program (runs as LocalSystem or the service virtual account), replacing programs an administrator later runs elevated from Bin, or planting a DLL in Bin that those programs load in place of the system copy. Limiting factors: no remote vector (local access needed), prior authentication required, and dependence on an administrator having chosen the insecure install path - the vulnerability does not exist under the default, recommended configuration. |
| Impact | This is a genuine but conditional local privilege-escalation issue (CWE-276, incorrect default permissions), not a remotely wormable threat. The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.8 HIGH) is internally consistent with the description: exploitation requires a local, already-authenticated low-privilege user (PR:L), and the high C/I/A impact reflects code execution as LocalSystem or the service virtual account. No EPSS score, KEV listing, SSVC decision, or POC is present in the input - exploitation status is therefore 'no public exploit identified at time of analysis', and there is no evidence of active exploitation. The single most important risk-reducing factor is that the default Program Files installation is NOT affected; the flaw only manifests when an administrator installs the product to a writable location such as the root of an NTFS drive, where Authenticated Users (client) or Users (server) inherit write access to Bin. This makes real-world risk strongly dependent on local deployment choices rather than a universal condition. Net assessment: a real, patch-worthy local EoC/EoP issue for environments with non-standard install paths, but not a drop-everything priority absent confirmation that affected hosts use a root/writable install location. The 7.8 score somewhat overstates practical exposure because it does not encode the non-default-path precondition. |
| Exploit ScenarioDerived | An administrator installs hMailServer 6.0.0-6.3.6 to a non-default path such as C:\hMailServer (the root of a drive), where the Bin folder inherits write permissions for Authenticated Users or Users. A local non-administrator user replaces the service executable or drops a malicious DLL into Bin; when the LocalSystem/virtual-account service (re)starts, or when an admin runs an elevated maintenance tool from Bin, the attacker's code executes with high privileges. No public proof-of-concept is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Local privilege escalation in Progressive Robot hMailServer 6.0.0 through 6.3.6 allows any authenticated, non-administrator user on the host to run code as LocalSystem or as the mail server's virtual service account, but only when the installer was pointed at a folder that inherits writable permissions from its parent, such as the root of an NTFS drive. The installer accepts any path without warning and creates neither the program folder nor its Bin subfolder with explicit permissions, so a drive-root install leaves Bin writable to Authenticated Users (Modify on Windows clients) or Users (create files and folders on Windows Server); the default Program Files installation grants ordinary users only read and execute and is explicitly not affected. No public exploit code or active exploitation is confirmed at time of analysis, and the reference to the v6.3.7 release indicates the vendor has shipped a fixed version.
RemediationAI
Vendor-released patch: hMailServer v6.3.7, available from https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.7; upgrade any 6.0.0-6.3.6 installation, and re-verify the ACLs after upgrading since the patch does not retroactively fix an already-permissive folder. Where upgrading is not immediately possible, two actionable compensating controls apply. First, relocate the installation to the default Program Files path, where inherited permissions grant ordinary users only read and execute. Second, if a non-default path must be retained, break inheritance on both the program folder and its Bin subfolder and apply an explicit DACL granting Full Control only to Administrators and SYSTEM, and Read & Execute to Users/Authenticated Users; verify the result with icacls and re-check after any reinstall, since a fresh install recreates the folders with inherited-only permissions. The trade-off is that other software or scripts that relied on inherited write access to that folder (for logs, config, or update drops) will break and must be granted narrow, explicit rights instead. As a detection measure, monitor the Bin directory for newly created or modified executables and DLLs, and audit service-start and elevated-administrator execution paths that resolve binaries from that folder. Environments already deployed at a drive root with default inheritance should be treated as potentially compromised and reviewed for unauthorized binaries.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-276 (Incorrect Default Permissions) in the Windows installer, which places hMailServer's executables in a Bin subfolder of the user-selected program folder and assigns that folder and Bin no explicit discretionary ACL entries. Without explicit ACEs, both directories simply inherit from their parent, and NTFS volume roots grant broad write rights by default: Authenticated Users receive Modify on Windows client SKUs, while Users receive create-files/create-folders on Windows Server. Because the mail server runs as LocalSystem (or as the service's virtual account), a local non-administrator who can write into Bin can achieve three distinct primitives: overwrite or replace the service binary for execution at service start or restart, replace utilities that an administrator later runs elevated out of Bin during setup and maintenance, or plant a DLL in Bin that those elevated processes load ahead of the system copy (classic DLL search-order/planting abuse). The CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H reflects that the attack is strictly local, needs no user interaction, requires only low-privileged authenticated access, and yields high confidentiality, integrity, and availability impact at unchanged scope. The vulnerability is configuration-dependent: on the default Program Files path the inherited ACLs give ordinary users read/execute only, so the flaw does not exist in the recommended deployment.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local low-privileged user (AV:L/PR:L) overwrites files in a writable Bin to gain LocalSystem execution, yielding full C/I/A on the host; the non-default install path is an environmental precondition, not attacker-controlled complexity.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
DescriptionCVE.org
Incorrect default permissions in the Windows installer of Progressive Robot hMailServer 6.0.0 through 6.3.6 allow a local authenticated user to run code as the mail server's high-privileged accounts when the product is installed in a folder whose permissions are inherited from a writable parent, such as the root of a drive. The installer places the server's programs in the Bin folder of the program folder and gives neither the program folder nor Bin any permissions of their own, so they inherit the parent's. Under the default location, Program Files, ordinary users receive only read and execute and the configuration is not affected; but the installer accepts any path without warning, and a program folder at the root of an NTFS volume inherits write access for a broad group - Authenticated Users (Modify) on a Windows client, Users (create files and folders) on Windows Server. A local user without administrator rights can then alter or replace the service program, which runs as LocalSystem or as the service's virtual account, or the programs an administrator runs elevated from Bin during setup and maintenance, or place a library in Bin that those programs load in place of the system copy, gaining code execution with those privileges. The default Program Files installation is not affected.
Articles & Coverage 1
Executive ViewAI
hMailServer versions 6.0.0 through 6.3.6 can allow a local non-administrative user to escalate to SYSTEM-level code execution when the product is installed in a parent-writable location such as a drive root, putting host integrity and mail data at risk only on those non-default deployments. Standard Program Files installations are not affected, so exposure is limited to a subset of servers, and no public exploit has been identified at time of analysis. Leadership should prioritize inventorying install paths and validating the v6.3.7 fixed release.
Apply vendor patch (v6.3.7 per advisory reference); if upgrade cannot be completed immediately, relocate the installation to a restrictive directory such as Program Files and remove Modify and create-file permissions for ordinary users on the install folder and Bin subfolder.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2026-104410
GHSA-xgwq-m9m9-pgw3
NVD
CVE.org
EPSS
Exploit-DB