Missing authorization on COM objects in Progressive Robot hMailServer 6.0.0 through 6.3.5 (Windows only) lets a local interactive user with no hMailServer credential read and write arbitrary files as the service account and queue mail as any sender. The service registers its COM classes with no DCOM access or launch permission and calls CoInitializeSecurity with no security descriptor, so any user logged on at the console or over Remote Desktop can activate the classes in the running service; a hMailServer.Message, its Attachments and Attachment, and a hMailServer.FetchAccount created this way carry a credential that never authenticated. Attachments.Add(path) and Attachment.SaveAs(path) performed no authorization check, and Message.Save/Copy and FetchAccount.AccountID/Save performed none either up to 6.3.3 and from 6.3.4 treated a holder with no credential as the server's own event-script host. Because the service does not impersonate the COM caller, Attachments.Add reads any file the service account can read and returns it, Attachment.SaveAs writes attacker-chosen bytes to any path it can write (on a LocalSystem installation, code execution as SYSTEM), Message.Save queues outbound mail from any address past the SMTP checks, and FetchAccount attaches a mail-fetch job to any mailbox. The objects an Application handed out behave the same once a later Authenticate on that Application fails.
CVE-2026-104660
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-08. A secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/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 computedSeverity78% × 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
- 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.6COM: objects without a credential read and wrote files as the service account and queued mail as any sender (#59) · Issues · hmailserver / hMailServer · GitLab
https://gitlab.com/hmailserver/hmailserver/-/work_items/59Vendor Advisories for CVE-2026-104660(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 12× in last 7d / 12× 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:21 UTCEG score recompute
- 2026-10-09 22:20 UTCGHSA enrichment
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-09 09:50 UTCGHSA enrichment
- 2026-10-08 21:19 UTCGHSA enrichment
- 2026-10-08 15:23 UTCEG score recompute
- 2026-10-08 15:23 UTCGHSA enrichment
- 2026-10-08 14:55 UTCEG score recompute
- 2026-10-08 14:55 UTCGHSA enrichment
- 2026-10-08 11:24 UTCEG score recompute
- 2026-10-08 10:57 UTCEG score recompute
- 2026-10-08 10:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-104660?
When was CVE-2026-104660 disclosed?
Is CVE-2026-104660 actively exploited?
What is the CVSS score of CVE-2026-104660?
How do I remediate CVE-2026-104660?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-104660
Is Your Infrastructure Affected by CVE-2026-104660?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.