CVE-2026-107566
Received Received - Intake

Authorization Bypass in hMailServer Leading to DKIM-Signed Email Spoofing

Vulnerability report for CVE-2026-107566, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-19

Last updated on: 2026-10-19

Assigner: GitLab Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-19
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Progressive Robot Ltd hMailServer 6.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in hMailServer allows authenticated users to manipulate email headers and forge DKIM-signed messages. It exists in the Sieve editheader action and mail-rule engine's Set header value action. Users can delete or modify headers like From, Sender, or DKIM-Signature before redirecting messages. The server then signs the altered message with the domain in the rewritten From header, making the forgery appear legitimate.

Detection Guidance

Check hMailServer logs for unusual header modifications in Sieve scripts or mail rules. Look for edits to From, Sender, DKIM-Signature, or other critical headers before forwarding or redirecting messages. Review scripts in the Sieve directory and mail-rule configurations for unauthorized header changes.

Impact Analysis

An attacker could send emails appearing to come from any address, including domains hosted on your server with DKIM enabled. This compromises email integrity and authenticity, potentially tricking recipients into trusting forged messages. It does not expose message content or affect server availability.

Mitigation Strategies

Upgrade hMailServer to version 6.3.7 or later to patch the vulnerability. Disable Sieve script surfaces if not required. Audit existing Sieve scripts and mail rules for suspicious header modifications, especially targeting From, Sender, or DKIM-Signature fields. Restrict user permissions to prevent unauthorized script or rule changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107566. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart