Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-107573 Overview
CVE-2026-107573 is an incorrect default permissions vulnerability [CWE-276] in the Windows installer of Progressive Robot hMailServer versions 6.0.0 through 6.3.5. The installer places critical server data under Program Files with permissions inherited from the installation folder, granting the local Users group read access. Any authenticated local user can read stored mail, logs, the built-in database containing account password hashes, and the hMailServer.INI configuration file. The configuration file holds the external database password sealed only with the machine DPAPI key, which any local account can unseal. The Linux AppImage builds 6.3.0 through 6.3.5 share an analogous flaw in per-user data folders.
Critical Impact
Any local authenticated user can read every stored message, extract password hashes, and recover the external database password, giving full control of the mail server's backing database.
Affected Products
- Progressive Robot hMailServer 6.0.0 through 6.3.5 (Windows installer)
- Progressive Robot hMailServer 6.3.0 through 6.3.5 (Linux AppImage)
- hMailServer data, log, temp, database, events folders and hMailServer.INI
Discovery Timeline
- 2026-10-08 - CVE-2026-107573 published to NVD
- 2026-10-08 - Last updated in NVD database
- v6.3.6 - Progressive Robot releases patched hMailServer version via GitLab
Technical Details for CVE-2026-107573
Vulnerability Analysis
The hMailServer Windows installer creates runtime directories and the primary configuration file inside the installation path, typically beneath C:\Program Files\hMailServer. The installer does not apply restrictive access control lists to these objects. Instead, the new folders and hMailServer.INI inherit the parent directory's default ACL, which grants the built-in Users group read access.
As a result, any interactive or remote-interactive account on the host can read mailbox stores, log files, and the embedded database. When the hMailServer service is stopped, the SQLite-style built-in database file is readable, exposing account password hashes. The configuration file further exposes the external database connection password. That value is sealed only with the machine-scope Data Protection API (DPAPI) key, which any local account can invoke to unseal the secret.
The Linux AppImage variants (6.3.0 through 6.3.5) exhibit a parallel flaw: per-user data folders are created with modes that permit other local users to read their contents.
Root Cause
The root cause is reliance on default inherited permissions rather than explicit hardening during installation [CWE-276]. The installer should restrict read access on data, log, database, and configuration objects to the hMailServer service account and administrators. Instead, it accepts the permissive ACL assigned to Program Files subdirectories, which includes read for the local Users group.
Attack Vector
Exploitation requires only local authenticated access with low privileges. An attacker signed in to the host navigates to the hMailServer installation directory and reads hMailServer.INI, log files, and the per-mailbox stores. The attacker calls CryptUnprotectData with the machine DPAPI scope to recover the external database password. If the mail service is stopped during maintenance or by a scheduled action, the attacker also reads the built-in database and extracts stored account password hashes for offline cracking.
No exploitation code is required beyond standard file reads and a short DPAPI unseal routine. Refer to the GitLab Work Item #77 for the maintainer's technical discussion.
Detection Methods for CVE-2026-107573
Indicators of Compromise
- Non-service accounts opening handles to hMailServer.INI, hMailServer.sdf, or files under the Data, Logs, Database, or Events subdirectories.
- Processes other than hMailServer.exe invoking CryptUnprotectData against blobs sourced from the hMailServer configuration.
- Unexpected copies of mail store files or configuration files appearing in user profile paths or removable media.
Detection Strategies
- Enable Windows object access auditing (SACL) on the hMailServer installation directory and alert on read access from any principal outside the service account and administrators.
- Hunt in endpoint telemetry for file reads to hMailServer.INI by processes other than hMailServer.exe or installer processes.
- On Linux, monitor access to AppImage per-user data folders using auditd watches on the data directory paths.
Monitoring Recommendations
- Baseline which service and administrative accounts legitimately touch hMailServer paths and alert on deviations.
- Correlate service stop events (Service Control Manager event ID 7036 with state stopped) with subsequent read access to the built-in database file.
- Review file integrity monitoring for permission changes on hMailServer directories after patch deployment to confirm hardening.
How to Mitigate CVE-2026-107573
Immediate Actions Required
- Upgrade hMailServer to version 6.3.6 or later using the release available on the GitLab Release v6.3.6 page.
- Rotate the external database password after upgrading, since the previous value may have been exposed to any local account.
- Force a password reset for all hMailServer mailbox accounts whose hashes were readable while the service was stopped.
Patch Information
Progressive Robot addressed the issue in hMailServer 6.3.6. The release notes and fix discussion are published on the project's GitLab tracker. Review the GitLab Release v6.3.6 notes and the associated GitLab Work Item #77 for implementation details.
Workarounds
- Restrict ACLs on the hMailServer installation directory, data folders, database folder, logs, and hMailServer.INI so that only the service account and administrators have read access.
- Relocate the data, log, and database directories outside Program Files to a dedicated path with explicit permissions.
- On Linux AppImage installations, change ownership and mode of per-user data folders to restrict access to the hMailServer runtime user only.
# Example: restrict read access on Windows hMailServer directories
icacls "C:\Program Files\hMailServer" /inheritance:r
icacls "C:\Program Files\hMailServer" /grant:r "Administrators:(OI)(CI)F" "SYSTEM:(OI)(CI)F" "NT SERVICE\hMailServer:(OI)(CI)M"
icacls "C:\Program Files\hMailServer\hMailServer.INI" /inheritance:r
icacls "C:\Program Files\hMailServer\hMailServer.INI" /grant:r "Administrators:F" "SYSTEM:F" "NT SERVICE\hMailServer:R"
# Example: tighten Linux AppImage per-user data folder
chown -R hmailserver:hmailserver /home/hmailserver/.hmailserver
chmod -R go-rwx /home/hmailserver/.hmailserver
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

