# CVE-2026-104660: Missing Authorization in hMailServer

> Local users can exploit missing COM authorization in hMailServer to read/write arbitrary files and execute code as SYSTEM.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-p223-vjjq-q36p

## What is CVE-2026-104660?

CVE-2026-104660 is a high-severity missing authorization vulnerability in Progressive Robot Ltd hMailServer, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-104660?


## How do I fix CVE-2026-104660?

No fix has been published for CVE-2026-104660 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104660 being exploited?

There is no known exploitation of CVE-2026-104660 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104660 and fix it if it is affected.

What it is: CVE-2026-104660 is a high-severity missing authorization vulnerability in Progressive Robot Ltd hMailServer, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104660 in the wild and no public exploit code.

Affected product: Progressive Robot Ltd hMailServer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104660/ (Markdown: https://insights.sbomify.com/CVE-2026-104660/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104660
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104660
- OSV: https://osv.dev/vulnerability/CVE-2026-104660

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104660/
Summaries are generated and may contain mistakes; the official description above is the record.