# CVE-2026-114473: Incorrect Authorization in hMailServer


- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-mvr2-pg72-p566

## What is CVE-2026-114473?

CVE-2026-114473 is a medium-severity vulnerability in Progressive Robot Ltd hMailServer, published on 21 Oct 2026. 

### Official description

Incorrect authorization in the Sender Rewriting Scheme (SRS) of Progressive Robot hMailServer 6.2.1 through 6.3.6 allows a remote attacker to relay mail through the server to outside addresses. With SRS enabled, the server rewrites the envelope sender of mail it forwards to a signed SRS address at the forwarding domain, and passes a bounce to that address back to the original sender; but it took every message to a valid SRS address, whatever its sender, as delivery to a local recipient, so the relay rules and the SMTP authentication they require were not applied, and the message was delivered to the outside address the SRS address encodes. Anyone holding a valid SRS address of the server, such as the recipient of a forwarded message, could have the server relay mail to the address it encodes for 21 days, and an account holder whose account forwards to an outside mailbox could obtain one for any address. SRS is off by default.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-114473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114473 is a medium-severity vulnerability in Progressive Robot Ltd hMailServer, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114473 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-114473/ (Markdown: https://insights.sbomify.com/CVE-2026-114473/index.md)
```

## Sources

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

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