Quick answers
- Is CVE-2026-114475 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114475 being exploited in the wild.
- How severe is CVE-2026-114475?
- Medium severity, with a CVSS score of 6.5, published 21 October 2026.
- Which products and versions are affected?
- Progressive Robot hMailServer 6.3.4 through 6.3.6.
- Is there a fix for CVE-2026-114475?
- Yes: fixed in hMailServer 6.3.7. Until then: On multi-tenant servers, do not issue full-scope API keys or assign serveradmin confined to named domains to untrusted parties; keep the REST API disabled (RestApiPort = 0, the default) where not needed; and review custom roles for unauthorized permission changes made by confined credentials.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-21"},{"kind":"patched","at":"2026-10-21","note":"v6.3.7 released"},{"kind":"other","at":"2026-10-13","note":"Found in project's web-surface review"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114475 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-114475?
- Check whether you run Progressive Robot hMailServer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: hMailServer 6.3.7
On multi-tenant servers, do not issue full-scope API keys or assign serveradmin confined to named domains to untrusted parties; keep the REST API disabled (RestApiPort = 0, the default) where not needed; and review custom roles for unauthorized permission changes made by confined credentials.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-21"},{"kind":"patched","at":"2026-10-21","note":"v6.3.7 released"},{"kind":"other","at":"2026-10-13","note":"Found in project's web-surface review"}]
Technical details
Missing authorization checks in three REST API endpoints (`POST /api/v1/roles`, `PUT /api/v1/roles/{name}`, `DELETE /api/v1/roles/{name}`) fail to validate domain scope for a confined serveradmin credential. An authenticated user with manage_roles permission confined to named domains can create, modify, or delete custom roles that are assigned across other domains, bypassing the authorization gate that should refuse these operations to non-global administrators.
Affected products
- Progressive Robot hMailServer 6.3.4 through 6.3.6