CVE-2026-107578

MEDIUMPre-NVD 6.76.7
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-94860 (ENISA EUVD) · GHSA-f2xp-4p4c-fpc3 (GitHub Security Advisories)Source: ENISA EUVD

6.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 6.7Exploit: None knownExposed services: Not assessed

Upgrade to hMailServer 6.3.6, in which every administrative command writes nothing to the logs and arms no crash recorder, writes the certificate only through folders held open and checked from the drive's root, reaches… (from the CVE record's solution, GitLab Inc.) — apply it.

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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity67% × 45%
Impact severity (EG Severity): CVSS 6.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation<0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade to hMailServer 6.3.6, in which every administrative command writes nothing to the logs and arms no crash recorder, writes the certificate only through folders held open and checked from the drive's root, reaches… (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.7): severity, escalated by confirmed exploitation. This CVE's 6.7 is its impact severity (EG Severity), not escalated.

EG Severity
6.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

Upgrade to hMailServer 6.3.6, in which every administrative command writes nothing to the logs and arms no crash recorder, writes the certificate only through folders held open and checked from the drive's root, reaches… (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 8, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Fix named in the CVE record's solution (GitLab Inc.).
Web page

hMailServer 6.3.6 · hmailserver / hMailServer · GitLab

https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6
Web page

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 3× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-31 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-10-31 11:25 UTCOSV refresh
  3. 2026-10-28 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-10-25 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-25 14:54 UTCEG score recompute
  6. 2026-10-23 08:41 UTCEG score recompute
  7. 2026-10-23 08:40 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
  8. 2026-10-19 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-18 05:07 UTCEG score recompute
  10. 2026-10-12 16:38 UTCEG score recompute
  11. 2026-10-11 23:41 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
  12. 2026-10-11 20:14 UTCEG score recompute
  13. 2026-10-11 18:26 UTCEG score recompute
  14. 2026-10-11 15:00 UTCEG score recompute
  15. 2026-10-10 22:52 UTCEG score recompute
  16. 2026-10-10 22:52 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
  17. 2026-10-10 19:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-09 22:06 UTCEG score recompute
  19. 2026-10-09 22:06 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-10-08 21:18 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
  22. 2026-10-08 15:23 UTCEG score recompute
  23. 2026-10-08 15:23 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
  24. 2026-10-08 14:49 UTCEG score recompute
  25. 2026-10-08 14:49 UTCGHSA enrichmentGHSA-f2xp-4p4c-fpc3 · GitHub CVSS 6.7
Show 3 more
  1. 2026-10-08 12:26 UTCEG score recompute
  2. 2026-10-08 11:57 UTCEG score recomputeFirst assessed: 6.7 MEDIUM
  3. 2026-10-08 11:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107578?
CVE-2026-107578 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-107578 published?
The CVE record for CVE-2026-107578 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
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?
The CVE record's solution for CVE-2026-107578, written by its CNA GitLab Inc., names the fix: "Upgrade to hMailServer 6.3.6, in which every administrative command writes nothing to the logs and arms no crash recorder, writes the certificate only through folders held open and checked from the drive's root, reaches…" 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.

Book a Demo →Browse All CVEs