Description
Missing authorization in the Sieve notify action (6.2.22 through 6.3.6) and in the mail-rule Reply action (6.0.0 through 6.3.6) of Progressive Robot hMailServer allows an authenticated user to send mail through the server as any address. A Sieve notify sends a notification message, and its :from tag names the sender; the server set the notification's From header to that :from as the script wrote it, without checking that the address belongs to the account - the check that the Sieve vacation action applies to its own :from, and that the server applies to the sender of mail queued over COM or sent from the webmail. An account that can store a Sieve script (over ManageSieve, the REST API's self-service filter, or the administration interface) could therefore have the server send a notification from any address, on this server or anywhere; and where the claimed address is at a domain the server hosts with DKIM signing enabled, the server signed the notification with that domain's DKIM key, because it signs by the From header's domain, producing forged mail aligned to pass the domain's DMARC policy. The notify action and this behaviour were introduced in 6.2.22. In the mail-rule engine, a rule's Reply was likewise sent from whatever address the action named, whoever the rule belonged to, so that an account acting on its own rules over COM, a domain administrator, or an API key confined to a domain (over the REST API from 6.3.4) could have a domain's or an account's rule reply from any address, signed, where that address is at a domain the server hosts with DKIM signing enabled, with that domain's key.
Published: 2026-10-19
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: Send forged emails with valid DKIM signatures
Action: Apply patch
AI Analysis

Impact

The vulnerability is a missing authorization check in the Sieve notify action and the mail‑rule Reply action of Progressive Robot’s hMailServer. An authenticated user who can store a Sieve script or create a mail rule can cause the server to send a message where the From header is any address, including addresses that belong to domains hosted on the same server. When the chosen address is at a domain that is DKIM signed by the server, the generated message will be signed with that domain’s key, allowing the forged mail to pass DMARC checks and appear authentic to recipients. This capability is effectively impersonation of any address at the domain and can be used to send spam, phishing, or business‑email‑spoofing messages. The impact is that an attacker can transmit mail that appears to be from trusted domains without any further authorization.

Affected Systems

The flaw affects hMailServer versions 6.2.22 through 6.3.6 for the Sieve notify action, and 6.0.0 through 6.3.6 for the mail‑rule Reply action. Any installation of hMailServer within those version ranges that allows users to create or store Sieve scripts (via ManageSieve, the REST API, or the administrative interface) or author mail rules is vulnerable.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. The EPSS score is not available, but the lack of a KEV listing suggests that exploitation has not been observed at scale yet. Nevertheless, because the attack requires only authenticated access—something that is typically easy to obtain on a mail server—and produces forged mail that can bypass common email authenticity checks, the risk to organizations that host user domains is non‑trivial. An attacker can therefore use the vulnerability to distribute mass phishing campaigns or to trick recipients into believing messages originate from legitimate senders.

Generated by OpenCVE AI on October 19, 2026 at 16:22 UTC.

Remediation

Vendor Solution

Upgrade to hMailServer 6.3.7, which uses a Sieve notify :from only when it is an address that reaches the account (the account's own address or an active alias of it) - otherwise the notification goes from the account's own address, logged - and refuses a notify :from that is not an address when the script is stored, as the vacation action already does; and which sends a reply of an account's or a domain's mail rule only from an address the rule's owner may send as, refusing any other when the rule is saved and not sending a reply stored with one before (logged). Until then, where accounts need not set Sieve scripts, close the script surfaces: keep ManageSieve off (ManageSieveServerPort=0, the default) or bound to the loopback, and turn the REST API off where the webmail's filter editor is not wanted (RestApiPort=0, the default); and review active Sieve scripts for a notify whose :from is not the account's own address or an alias of it, and account and domain rules for a reply from an address the rule's owner may not send as. There is no per-extension setting that turns notify off while Sieve is in use.


OpenCVE Recommended Actions

  • Upgrade hMailServer to version 6.3.7, which correctly validates the :from address in Sieve notify and mail‑rule Reply actions.
  • If an upgrade is not immediately possible, block Sieve script uploads by setting ManageSieveServerPort=0 or binding the service to the loopback interface.
  • Turn off the REST API for the webmail filter editor by configuring RestApiPort=0 when that functionality is not required.

Generated by OpenCVE AI on October 19, 2026 at 16:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 15:45:00 +0000

Type Values Removed Values Added
Description Missing authorization in the Sieve notify action (6.2.22 through 6.3.6) and in the mail-rule Reply action (6.0.0 through 6.3.6) of Progressive Robot hMailServer allows an authenticated user to send mail through the server as any address. A Sieve notify sends a notification message, and its :from tag names the sender; the server set the notification's From header to that :from as the script wrote it, without checking that the address belongs to the account - the check that the Sieve vacation action applies to its own :from, and that the server applies to the sender of mail queued over COM or sent from the webmail. An account that can store a Sieve script (over ManageSieve, the REST API's self-service filter, or the administration interface) could therefore have the server send a notification from any address, on this server or anywhere; and where the claimed address is at a domain the server hosts with DKIM signing enabled, the server signed the notification with that domain's DKIM key, because it signs by the From header's domain, producing forged mail aligned to pass the domain's DMARC policy. The notify action and this behaviour were introduced in 6.2.22. In the mail-rule engine, a rule's Reply was likewise sent from whatever address the action named, whoever the rule belonged to, so that an account acting on its own rules over COM, a domain administrator, or an API key confined to a domain (over the REST API from 6.3.4) could have a domain's or an account's rule reply from any address, signed, where that address is at a domain the server hosts with DKIM signing enabled, with that domain's key.
Title Missing Authorization in hMailServer
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-10-19T15:34:22.493Z

Reserved: 2026-10-08T10:51:05.636Z

Link: CVE-2026-107568

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T16:17:01.717

Modified: 2026-10-19T16:17:01.717

Link: CVE-2026-107568

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T16:30:13Z

Weaknesses