Improper link resolution and external control of file paths in the administrative command-line operations of hMailServer.exe in Progressive Robot hMailServer 6.3.4 and 6.3.5 allow a local attacker who already runs code as the low-privilege service account to escalate privilege. On Windows, operations run with administrator rights by the installer, DBSetup, the Control Panel or an administrator wrote log entries and crash records into the log folder, created, deleted and changed the permissions of the self-signed certificate and private key in the data folder, and rewrote message files in the data folder, all by path in folders the service account (NT SERVICE\hMailServer, the default for new installations since 6.3.4) can modify, following junctions and mount points; and the store-maintenance operations reached files by names taken from the database, which the service account can write, including names outside the data folder. On Linux, the store-maintenance and object-storage operations run as root followed symbolic links the service account (the packaged hmailserver user, which owns the data folder) planted in it, so a root-run operation read, wrote or removed the link's target as root. A local attacker controlling the service account can thereby gain the administrator's (Windows) or root's (Linux) privileges when such an operation is run.
CVE-2026-107578
Score 6.7 from GitHub Security Advisory published 2026-10-08. A secondary CVSS source baseline 6.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 6.7
- EG Score
- 6.7MEDIUMhigh confidence
- EG Risk
- 30EG Risk 30/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity67% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 8, 2026
Last Modified
October 8, 2026
Advisory Details (2)
Auto-updated Oct 8, 2026hMailServer 6.3.6 · hmailserver / hMailServer · GitLab
https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6Administrative commands followed links and paths the service account controls (Windows commands run elevated, Linux commands run as root), so code running as the service could escalate (#71) · Issues · hmailserver / hMailServer · GitLab
https://gitlab.com/hmailserver/hmailserver/-/work_items/71Vendor Advisories for CVE-2026-107578(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 22:06 UTCEG score recompute
- 2026-10-09 22:06 UTCGHSA enrichment
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-08 21:18 UTCGHSA enrichment
- 2026-10-08 15:23 UTCEG score recompute
- 2026-10-08 15:23 UTCGHSA enrichment
- 2026-10-08 14:49 UTCEG score recompute
- 2026-10-08 14:49 UTCGHSA enrichment
- 2026-10-08 12:26 UTCEG score recompute
- 2026-10-08 11:57 UTCEG score recompute
- 2026-10-08 11:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-107578?
When was CVE-2026-107578 disclosed?
Is CVE-2026-107578 actively exploited?
What is the CVSS score of CVE-2026-107578?
How do I remediate CVE-2026-107578?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-107578
Is Your Infrastructure Affected by CVE-2026-107578?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.