CVE-2026-107578

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreHIGH confidence

Score 6.7 from GitHub Security Advisory published 2026-10-08. A secondary CVSS source baseline 6.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 6.7Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
6.7
EG Score
6.7MEDIUMhigh confidence
EG Risk
30
EG 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 computed
Severity67% × 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, 2026
No fix on record yet.
generic

hMailServer 6.3.6 · hmailserver / hMailServer · GitLab

https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6
generic

Administrative 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/71

Vendor 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.

  1. 2026-10-09 22:06 UTCEG score recompute
  2. 2026-10-09 22:06 UTCGHSA enrichment
  3. 2026-10-09 20:06 UTCEPSS rescore
  4. 2026-10-08 21:18 UTCGHSA enrichment
  5. 2026-10-08 15:23 UTCEG score recompute
  6. 2026-10-08 15:23 UTCGHSA enrichment
  7. 2026-10-08 14:49 UTCEG score recompute
  8. 2026-10-08 14:49 UTCGHSA enrichment
  9. 2026-10-08 12:26 UTCEG score recompute
  10. 2026-10-08 11:57 UTCEG score recompute
  11. 2026-10-08 11:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-107578?
CVE-2026-107578 is a medium vulnerability published on October 8, 2026. 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,…
When was CVE-2026-107578 disclosed?
CVE-2026-107578 was first published on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-107578 actively exploited?
CVE-2026-107578 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107578?
CVE-2026-107578 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107578?
No fix for CVE-2026-107578 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-107578 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-107578

Explore →

Is Your Infrastructure Affected by CVE-2026-107578?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.