Skip to main content
Vulnerability Database/CVE-2026-114478

CVE-2026-114478: hMailServer Auth Bypass Vulnerability

CVE-2026-114478 is an authentication bypass flaw in Progressive Robot hMailServer 6.0.0 through 6.3.6 that allows attackers to bypass DMARC policies through mail forwarding. This post explains its impact, affected versions, and mitigation steps.

Published:

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-114478 Overview

CVE-2026-114478 is a mail forwarding flaw in Progressive Robot hMailServer versions 6.0.0 through 6.3.6. The server fails to preserve the original sender context when forwarding mail that originated from outside the organization. An unauthenticated remote attacker can craft messages that, after being relayed through a hosted account's forward, alias, mailing list, or Sieve redirect, inherit an SMTP identity aligned with the hosted domain. Downstream receivers then evaluate SPF and DMARC against the forwarding server's identity rather than the message's true origin, allowing spoofed mail to pass DMARC. The weakness is classified under CWE-441: Unintended Proxy or Intermediary.

Critical Impact

Attackers can deliver spoofed email that passes DMARC alignment for any domain hosted by a vulnerable hMailServer instance, enabling convincing phishing and brand impersonation against external recipients.

Affected Products

  • Progressive Robot hMailServer 6.0.0 through 6.3.6
  • Deployments with account-level forwards, mail rule forwards, Sieve redirects, or list/alias expansions to external addresses
  • Instances with Sender Rewriting Scheme (SRS) or envelope sender rewrite enabled, or hosting subdomains whose SPF record authorises the server

Discovery Timeline

  • 2026-10-21 - CVE-2026-114478 published to the National Vulnerability Database
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114478

Vulnerability Analysis

The flaw is an authentication-context handling defect in hMailServer's forwarding pipeline. When the server relays a copy of externally received mail through a forward, alias, Sieve redirect, or list expansion, it assigns the outgoing copy an SMTP envelope identity associated with the organisation of the domain named in the message's From header. The original message's authentication posture is discarded.

Several envelope-sender outcomes are possible depending on configuration. With SRS or envelope rewrite enabled, the envelope sender is set to an address at the forwarding domain. For list traffic, the list's bounce address is used. Messages with an empty envelope sender are relayed under the server's host name with no envelope sender. An envelope sender arriving at a subdomain of a hosted domain is preserved as-is.

In each case, if the resulting identity resolves to an SPF record that authorises the hMailServer host, the receiver's SPF check passes for a domain aligned with the From header. DMARC then passes on the forwarded copy, even though the original inbound message never passed DMARC at the forwarding server. The DKIM-based variant of this bypass is tracked separately as CVE-2026-107567.

Root Cause

The server treats the act of forwarding as a trusted re-origination. It attaches outbound SMTP identity based on the message's claimed From domain and local configuration, rather than preserving the external provenance or breaking DMARC alignment. SRS, when enabled, compounds the problem because it rewrites envelope senders into the forwarding domain unconditionally, including for messages the server should not vouch for.

Attack Vector

Exploitation requires a hosted domain on the vulnerable server that forwards mail to an external destination. The attacker sends a message with a spoofed From naming the hosted domain to the forwarding address. The server relays the copy outbound with an SMTP identity whose SPF covers the hMailServer host, producing DMARC-aligned delivery at the external recipient. Preconditions include one of: SRS or envelope rewrite enabled; a list bounce address in the hosted domain's organisation; an envelope sender at a subdomain with permissive SPF; or an empty envelope sender combined with an SPF record authorising the server under its host name. No authentication is required. Attack complexity is high because the attacker must identify a qualifying forwarder and matching configuration.

See the hMailServer Work Item #90 for the maintainer's technical write-up.

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 Attacks

Detection Methods for CVE-2026-114478

Indicators of Compromise

  • Outbound SMTP messages where the envelope sender domain belongs to a hosted domain but the Received chain shows the message originated externally.
  • DMARC aggregate (rua) reports from third-party receivers showing SPF-pass, DMARC-pass results for mail that was relayed through forwarding addresses rather than authored on the server.
  • Inbound messages addressed to known forwarding aliases whose From header spoofs a locally hosted domain.

Detection Strategies

  • Correlate inbound mail logs with outbound forwarding logs to flag cases where a hosted-domain From arrives from an untrusted peer and is re-emitted under a hosted-domain envelope.
  • Parse DMARC aggregate reports for hosted domains and alert on pass results that correspond to IP addresses or source domains the organisation does not control.
  • Review hMailServer configuration for enabled SRS, envelope sender rewriting, mailing list bounce addresses, and SPF records covering subdomains to enumerate exploitable paths.

Monitoring Recommendations

  • Centralise hMailServer SMTP transaction logs and DMARC rua/ruf feedback into a SIEM for cross-source correlation.
  • Baseline normal outbound forwarding volume per alias and alert on sudden increases in forwarded mail with spoof-indicative header patterns.
  • Monitor for new or modified forwards, aliases, and Sieve rules on hosted accounts, which can be abused to establish an exploitation path.

How to Mitigate CVE-2026-114478

Immediate Actions Required

  • Upgrade hMailServer to version 6.3.7 or later, which addresses the forwarding identity preservation issue.
  • Audit all account forwards, mail rules, Sieve redirects, aliases, and mailing lists that deliver hosted-domain mail to external recipients.
  • Disable the Sender Rewriting Scheme and envelope sender rewrite on forwarding if they are enabled and not strictly required.

Patch Information

The maintainer has released a fix in hMailServer 6.3.7. Administrators should test the release in a staging environment and roll it out to production mail servers. The companion DKIM-route issue, CVE-2026-107567, is addressed in the same release lineage and should be remediated together.

Workarounds

  • Tighten SPF records for hosted domains and their subdomains so they do not broadly authorise the hMailServer host for arbitrary envelope senders.
  • Set mailing list bounce addresses to a dedicated domain that is not aligned with any hosted sender domain, breaking DMARC alignment on list traffic.
  • Reject or quarantine inbound mail whose From header claims a locally hosted domain when it arrives from an external source, before it reaches any forwarding alias.
bash
# Configuration example - disable envelope sender rewriting and SRS in hMailServer
# Review via the Administrator console or COM API, for example:
#   Settings.AntiSpam.SpfEnabled = True
#   Domain.SignatureEnabled = False  # review per-domain forwarding behavior
# Then upgrade to 6.3.7:
#   https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.7

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.