Description
Missing authorization in the Sieve editheader action (6.2.22 through 6.3.6) and in the mail-rule Set header value action (6.0.0 through 6.3.6) of Progressive Robot hMailServer allows an authenticated user to make the server send mail as any address, DKIM-signed where the address is at a domain the server signs for. A Sieve script's editheader (addheader/deleteheader) could add or delete any header field except Received and Return-Path, and the server applies a script's header edits before it queues a redirect, so the redirected copy is sent as the script left it. The server signs a message's first delivery pass as the domain named in its From header wherever it signs DKIM for that domain and the message carries no signature of it. A script could therefore delete and re-add From - another account's address, or anyone's at a hosted domain - and redirect, so the server sent the message in that name and, for a hosted domain, signed it with that domain's DKIM key, a forgery aligned to pass the domain's DMARC; or, where another sender's domain is one the server signs for, delete the DKIM-Signature that sender's message arrived with, alter a field, and redirect, so the server re-signed the altered message as that sender's domain. editheader placed no restriction on From, Sender, Resent-From, Resent-Sender or DKIM-Signature. The editheader action was introduced in 6.2.22. In the mail-rule engine, a domain's or an account's rule's Set header value action could likewise set From, Sender, Resent-From, Resent-Sender or DKIM-Signature ahead of a forward or a copy, 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 the server forward or copy a message in the name of 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: Sender spoofing and DKIM forging via missing authorization
Action: Immediate Patch
AI Analysis

Impact

The vulnerability permits an authenticated user to use Sieve’s *editheader* action or the mail‑rule "Set header value" action to modify any outgoing message header—including From, Sender, Resent‑From, Resent‑Sender, and DKIM‑Signature—except Received and Return‑Path. Because hMailServer signs the first delivery pass with the DKIM key for the domain named in the From header, an attacker can forge the From address, delete and re‑add it to a different sender, and redirect the message, resulting in a DKIM‑signed email that appears authentic and may pass DMARC checks. This facilitates phishing, domain spoofing, and other email‑based attacks.

Affected Systems

The flaw affects Progressive Robot Ltd’s hMailServer across all releases from 6.2.22 through 6.3.6 inclusive. Any instance employing Sieve scripts or account/domain mail‑rules that alter header values is vulnerable, regardless of whether the server is exposed externally or internally.

Risk and Exploitability

With a CVSS score of 6.5 the vulnerability is rated moderate severity, and though no EPSS value is published, the existence of an authenticated exploitation path increases the risk. The flaw is not currently listed in CISA’s Known Exploited Vulnerabilities catalog. An attacker only needs valid account credentials, a domain‑administrator role, or an API key to deploy a Sieve script or rule that forwards or copies mail with a forged identity and legitimate DKIM signature, thereby compromising the integrity and authenticity of outbound messages.

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

Remediation

Vendor Solution

Upgrade to hMailServer 6.3.7, which refuses a Sieve script that adds or deletes From, Sender, Resent-From, Resent-Sender or DKIM-Signature when the script is stored, and does not make such an edit at delivery for a script stored earlier (logged), while leaving Reply-To and other fields editable; and which lets only a server rule's Set header value action, which only the server administrator saves, set those five fields, refusing an account's or a domain's rule that sets one when it is saved and not setting it at delivery for one stored 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 an addheader or deleteheader of From, Sender, Resent-From, Resent-Sender or DKIM-Signature followed by a redirect, and account and domain rules for a Set header value of one of those fields. There is no per-extension setting that turns editheader off while Sieve is in use.


OpenCVE Recommended Actions

  • Upgrade hMailServer to version 6.3.7, which blocks editing of the protected header fields and prevents unauthorized DKIM signing.
  • If an upgrade cannot be performed immediately, disable the ManageSieve surface by setting ManageSieveServerPort=0 or binding it to the loopback interface, and disable the REST API by setting RestApiPort=0 if the webmail filter editor is not required.
  • Review all active Sieve scripts and account/domain mail‑rules for any addheader/deleteheader or Set header value actions that modify From, Sender, Resent‑From, Resent‑Sender, or DKIM‑Signature, and remove or restrict them before the server processes redirection or forwarding.

Generated by OpenCVE AI on October 19, 2026 at 16:21 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 editheader action (6.2.22 through 6.3.6) and in the mail-rule Set header value action (6.0.0 through 6.3.6) of Progressive Robot hMailServer allows an authenticated user to make the server send mail as any address, DKIM-signed where the address is at a domain the server signs for. A Sieve script's editheader (addheader/deleteheader) could add or delete any header field except Received and Return-Path, and the server applies a script's header edits before it queues a redirect, so the redirected copy is sent as the script left it. The server signs a message's first delivery pass as the domain named in its From header wherever it signs DKIM for that domain and the message carries no signature of it. A script could therefore delete and re-add From - another account's address, or anyone's at a hosted domain - and redirect, so the server sent the message in that name and, for a hosted domain, signed it with that domain's DKIM key, a forgery aligned to pass the domain's DMARC; or, where another sender's domain is one the server signs for, delete the DKIM-Signature that sender's message arrived with, alter a field, and redirect, so the server re-signed the altered message as that sender's domain. editheader placed no restriction on From, Sender, Resent-From, Resent-Sender or DKIM-Signature. The editheader action was introduced in 6.2.22. In the mail-rule engine, a domain's or an account's rule's Set header value action could likewise set From, Sender, Resent-From, Resent-Sender or DKIM-Signature ahead of a forward or a copy, 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 the server forward or copy a message in the name of 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:27.491Z

Reserved: 2026-10-08T10:50:55.763Z

Link: CVE-2026-107566

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

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

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

Link: CVE-2026-107566

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

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

Weaknesses