Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-126624Unverified Ownership in hMailServer

Description

Unverified ownership in the Windows installer of Progressive Robot hMailServer 6.3.7 allows a local authenticated user to run code as the mail server's service account or as an administrator when setup installs into, or upgrades, a program folder that accounts other than the administrators could write before, such as one made beforehand at 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 setup refused nothing that was already in them, or in the folders that hold the event script, the add-ons and the database scripts: a program, a library, a script or a settings file that another account owns, or whose own permissions let another account change it, is kept with that owner and those permissions, which the hardening of the folders does not take away. Setup then runs programs from Bin with the administrator's elevated rights, and the service, which runs as LocalSystem or as its virtual account, runs them and the event script, so that a library such an account placed in Bin is loaded in place of the system's; the account can still change the file after the installation. The default installation under Program Files is not affected.

Timeline

  1. ID reserved

    By GitLab

  2. Published

  3. · 6 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-126624, by who scored it
Scored byCVSSScoreVector
GitLabCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

What to do

Solution: Upgrade to hMailServer 6.3.8, whose setup looks, before it stops the service and again once the folders are hardened, at everything in Bin and ControlPanel, on the program folder's own level, and in Addons, Events, DBScripts, WebAdmin, Languages and MySQL, and refuses with exit code 7 to install where a program, a library, a script, a settings file or a folder there is owned by anybody but SYSTEM, the Administrators or TrustedInstaller, has an owner that cannot be read, or has an entry of its own that lets another account change it, naming each with the icacls that deals with it and a restart of Windows before setup runs again. Until then, install hMailServer under Program Files, or into a new folder inside one that only administrators may change. Before running setup into or over a program folder that other accounts could write, list the owners from an elevated Command Prompt - dir /q /a "<program folder>" and dir /q /s /a over its Bin, ControlPanel, Events, WebAdmin, DBScripts, Addons, Languages and MySQL, as the hMailServer documentation, ServiceAccount.md, "Before upgrading an installation at a drive's root", gives them for all but MySQL - and the entries of their own, with icacls "<program folder>" and icacls "<folder>" /T over the same folders, where an entry not marked (I) that gives anybody but SYSTEM, the Administrators or TrustedInstaller a right to change the item is another account's (the service's own Modify on hMailServerApiKeys.ini in Bin apart); where anybody but those owns anything there, or has such an entry, do not install over it: reinstall into a new folder as that page's "Reinstalling into a new folder" says.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-126624 badge
[![CVE-2026-126624](https://cveledger.app/badge/CVE-2026-126624.svg)](https://cveledger.app/cve/CVE-2026-126624)

Record last updated .