Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114475 Overview
CVE-2026-114475 is a missing authorization vulnerability [CWE-862] in Progressive Robot hMailServer versions 6.3.4 through 6.3.6. The flaw affects the REST role-management routes used to create, update, and delete custom roles. A remote authenticated user holding a credential confined to specific named domains can modify custom roles assigned to accounts in other tenants. The server's authorization gate fails to refuse the three role routes when a confined credential targets a route that specifies no domain. This enables cross-tenant tampering with permissions on mailboxes and settings belonging to other domains.
Critical Impact
A tenant-scoped administrator can alter, create, or delete custom roles affecting other tenants, raising or lowering their permissions over mailboxes and settings.
Affected Products
- Progressive Robot hMailServer 6.3.4
- Progressive Robot hMailServer 6.3.5
- Progressive Robot hMailServer 6.3.6
Discovery Timeline
- 2026-10-21 - CVE-2026-114475 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114475
Vulnerability Analysis
hMailServer exposes REST routes that create, update, and delete custom roles. These routes require the manage_roles permission, which only the serveradmin role holds. Full-scope API keys issued for named domains, and serveradmin principals assigned a domain list, remain confined to those domains yet still hold manage_roles. The authorization gate does not refuse the three role routes when the caller is a confined credential and the route references no domain. A credential issued to one tenant can therefore reach into another tenant's custom roles. The attacker can grant another domain's role every permission over its mailboxes and settings, or strip permissions the role requires to function.
The damage boundary is partial. Custom roles cannot hold administer_server, administer_domain, or manage_roles. A confined credential cannot elevate itself or another account to a server administrator by rewriting a custom role.
Root Cause
The REST authorization check validates that the caller holds manage_roles but does not verify that the role being modified belongs to a domain within the caller's scope. The route accepts calls that omit a domain, bypassing tenant isolation entirely.
Attack Vector
Exploitation requires an authenticated REST session or API key with manage_roles permission scoped to any domain. The attacker issues create, update, or delete calls against the role-management endpoints targeting custom roles assigned to accounts in domains outside their scope. No user interaction is required. Technical details are documented in GitLab hMailServer Work Item #89.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114475
Indicators of Compromise
- REST API calls to role create, update, or delete endpoints originating from a credential confined to a different domain than the role being modified.
- Unexpected permission changes on custom roles held by accounts in multiple tenants.
- Deletion of custom roles that no account currently holds, performed by a confined credential.
Detection Strategies
- Audit hMailServer REST access logs for role-management route invocations and correlate the caller's domain scope against the role's domain assignments.
- Alert on role mutation requests where the request body or path omits a domain qualifier.
- Baseline role configurations and detect drift in custom role permission sets.
Monitoring Recommendations
- Enable verbose REST API logging on hMailServer and forward events to a central log platform for correlation.
- Track issuance and use of full-scope API keys and flag any role-management activity from keys scoped to a single tenant.
- Monitor for anomalous volumes of role create or delete calls within short time windows.
How to Mitigate CVE-2026-114475
Immediate Actions Required
- Upgrade hMailServer to version 6.3.7 or later, which contains the authorization fix.
- Rotate all full-scope API keys issued for named domains after upgrading.
- Review existing custom role definitions and account assignments for unauthorized changes.
Patch Information
Progressive Robot resolved the issue in hMailServer 6.3.7. The fix is published in the GitLab hMailServer Release 6.3.7 notes, with technical background in GitLab hMailServer Work Item #89.
Workarounds
- Restrict network access to the REST management interface to trusted administrative hosts only.
- Revoke serveradmin assignments that use a domain list where cross-tenant isolation is required, pending the upgrade.
- Avoid issuing full-scope API keys to tenant-scoped operators until the patched release is deployed.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

