Read the docs

Incorrect Default Permissions in hMailServer

Priority LOW 30CWE-276Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
Required
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

Incorrect default permissions in the Windows installer of Progressive Robot hMailServer 6.3.7 let a local authenticated user run code as the administrator who installs it, when it goes into a new program folder in a location where every user can write, such as a drive root. Inno Setup creates the folder with inherited permissions and replaces them only 33 to 139 milliseconds later, so any local account can place files in the new Bin folder. Setup runs Bin's programs with elevated rights, and they load a library placed there. The default Program Files installation is not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00112 1st percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Progressive Robot LtdhMailServer6.3.7—No fix listedCNA

Remediation

No fixed version is listed. Install hMailServer into the default location under Program Files, which is not affected, and do not install it into a new folder in a location where all users can write, such as the root of a drive.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-126625
  2. 2026-11-11 Alias added: GHSA-q63q-8h8v-j42v
  3. 2026-11-12 Priority changed: MEDIUM → LOW
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-64884 Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in hMailServer CVSS 3.1CRITICAL 9.8
  • TI-2026-76418 Unchecked loop limit in hMailServer lets remote attackers stop mail CVSS 3.1HIGH 7.5
  • TI-2026-69567 Inefficient processing in hMailServer stalls mail delivery CVSS 3.1HIGH 7.5
  • TI-2026-69565 Infinite loop in hMailServer MIME handling lets attackers stop mail CVSS 3.1HIGH 7.5
  • TI-2026-69564 Inefficient DKIM and ARC checks in hMailServer cause denial of service CVSS 3.1HIGH 7.5
  • TI-2026-69562 Inefficient JSON parsing in hMailServer lets attackers halt mail CVSS 3.1HIGH 7.5
See all 59 →

Sources