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-114489 Overview
CVE-2026-114489 is a missing authorization vulnerability [CWE-862] in the REST and COM administration APIs of Progressive Robot hMailServer versions 6.0.0 through 6.3.6. The flaw allows a remote authenticated user whose credentials are scoped to named domains to modify mail routing and domain configuration beyond their assigned scope on a multi-tenant server. Domain administrators, role-restricted accounts, API keys issued for named domains, and ordinary COM API users can abuse missing authorization checks to hijack mail flow for domains they do not own.
Critical Impact
An attacker with limited domain-scoped credentials can divert, deny, or intercept mail destined for other tenants on the same hMailServer instance and reach server-internal addresses or stored route credentials.
Affected Products
- Progressive Robot hMailServer 6.0.0 through 6.3.6
- hMailServer REST administration API
- hMailServer COM administration API
Discovery Timeline
- 2026-10-21 - CVE-2026-114489 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114489
Vulnerability Analysis
The vulnerability resides in how hMailServer enforces authorization on administrative operations exposed through its REST and COM APIs. The authorization gate did not refuse privileged routes to credentials confined to specific named domains, and handlers were not given the caller context. A domain administrator, a role-restricted account, or a full-scope API key issued for named domains can therefore invoke operations outside its scope.
Abusable operations include creating a domain alias for any name, renaming a domain to any name the server does not host, setting a rule's bind-to-address, send-using-route, or script-function action to reach server-owned addresses, retrieving a configured route's stored credentials, and setting a domain's relay host to an address on the server's own network. Over the COM API, any account can set the three rule actions on its own rules, and the script-function action executes at delivery time.
Root Cause
The authorization layer failed to associate the caller identity with the target domain or configuration object. Over COM, the domain-alias save performed no authorization check at all, the domain rename required only a domain administrator role, and a rule save required at most that the caller could change the rule's owner. This design matches [CWE-862: Missing Authorization].
Attack Vector
The attack requires network access and valid low-privileged credentials on a multi-tenant hMailServer instance. An attacker crafts REST or COM API calls that target domain aliases, domain renames, rule actions, or relay host settings for domains outside their scope. Successful exploitation diverts other tenants' mail to attacker-controlled addresses, exposes stored route credentials, or triggers server-side script execution during mail delivery.
Technical details are documented in the hMailServer 6.3.7 release notes and GitLab Work Item #86.
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-114489
Indicators of Compromise
- Unexpected creation or modification of domain aliases pointing to domains not owned by the acting account.
- Domain rename events in administrative logs where the target name is not hosted by the server.
- Rule action changes referencing bind-to-address, send-using-route, or script-function targeting server-local addresses.
- Modifications to a domain's relay host pointing to an address inside the server's own network.
Detection Strategies
- Audit REST and COM API call logs for administrative operations invoked by accounts confined to named domains.
- Correlate account scope metadata with the target of each configuration change to flag cross-tenant modifications.
- Alert on rule save operations whose action fields reference internal routes or script functions.
Monitoring Recommendations
- Enable verbose administrative logging on hMailServer and forward events to a centralized SIEM.
- Monitor mail flow metrics for sudden routing changes, bounced tenant mail, or relay traffic to unexpected hosts.
- Review API key issuance records and remove unused or over-scoped keys.
How to Mitigate CVE-2026-114489
Immediate Actions Required
- Upgrade hMailServer to version 6.3.7 or later on every multi-tenant deployment.
- Rotate all stored route credentials that may have been accessible to domain-scoped accounts.
- Review existing domain aliases, domain names, rule actions, and relay host configurations for unauthorized changes.
- Revoke or re-scope API keys that were issued with broader privileges than required.
Patch Information
Progressive Robot released hMailServer 6.3.7 to address the missing authorization conditions. The fix adds caller context to administrative handlers and enforces scope checks on domain alias saves, domain renames, rule action updates, and relay host changes. Refer to the hMailServer 6.3.7 release for full change details.
Workarounds
- Restrict network exposure of the REST and COM administration APIs to trusted management networks only.
- Avoid issuing domain-scoped credentials or API keys on shared multi-tenant servers until the patch is applied.
- Disable the COM administration API where it is not required for operations.
- Monitor and manually review all configuration changes until the upgrade is completed.
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

