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

CVE-2026-104658: hMailServer Live-Update RCE Vulnerability

CVE-2026-104658 is a privilege escalation RCE flaw in hMailServer live-update helper that allows unprivileged users to execute code as root. This post explains its technical details, affected versions, impact, and mitigation.

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

CVE-2026-104658 is a local privilege escalation vulnerability in the Linux live-update apply helper (hmailserver-update) shipped with Progressive Robot hMailServer 6.3.4 and 6.3.5. The helper runs as root and reads a request file written by the unprivileged hmailserver service account. That request file controls both the program used to verify an AppImage update's signature and the systemd unit stopped before the service account's files are read. An attacker who already executes code as the hmailserver service account can force arbitrary code execution as root. The flaw is tracked under [CWE-807: Reliance on Untrusted Inputs in a Security Decision].

Critical Impact

Any attacker with code execution as the hmailserver service account on a default .deb or .rpm installation can escalate to full root privileges on the host.

Affected Products

  • Progressive Robot hMailServer 6.3.4 (Linux)
  • Progressive Robot hMailServer 6.3.5 (Linux)
  • .deb, .rpm, and AppImage packages running under the live-update path unit

Discovery Timeline

  • 2026-10-08 - CVE-2026-104658 published to NVD
  • 2026-10-08 - Last updated in NVD database
  • Release 6.3.6 - Progressive Robot publishes fixed release via GitLab hMailServer Release 6.3.6

Technical Details for CVE-2026-104658

Vulnerability Analysis

The hmailserver-update helper is a privileged component invoked through a systemd path unit that watches for a request file. When the file appears, the helper executes as root to apply AppImage updates. The helper trusts two fields taken directly from that request: the path to the signature verification program and the name of the systemd unit to stop before reading the service account's files. Both fields are attacker-controllable because the request file is owned and written by the unprivileged hmailserver service account.

The helper therefore makes a security decision — which binary verifies the update, and which unit is stopped — based on input that a lower-privileged process fully controls. An attacker who has already compromised the mail service through another defect can substitute an attacker-controlled binary in place of the signature verifier or supply a malicious unit name, resulting in code running as root.

Root Cause

The root cause is [CWE-807]: the privileged helper relies on untrusted inputs sourced from a file writable by the hmailserver service account. There is no validation that the referenced verifier binary or systemd unit is trusted or expected. The privileged process effectively delegates its security boundary to an unprivileged caller.

Attack Vector

Exploitation requires local code execution as the hmailserver service account, typically achieved by chaining a separate remote flaw in the mail server. The attacker writes a crafted request file into the location monitored by the live-update path unit. The helper then launches the attacker-supplied signature verifier as root, or stops an attacker-chosen unit before processing files, allowing arbitrary root code execution. The default .deb and .rpm packages activate the path unit automatically, and AppImage installations running under that unit are equally exposed. Further technical context is documented in GitLab hMailServer Work Item #58.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-104658

Indicators of Compromise

  • Unexpected writes to the live-update request file path by the hmailserver service account outside normal update windows.
  • hmailserver-update invoking non-standard binaries as root, especially binaries located under writable directories owned by the service account.
  • Unexpected systemctl stop operations initiated by hmailserver-update against units unrelated to hMailServer.

Detection Strategies

  • Audit execve calls made by hmailserver-update and alert when the executed path differs from the vendor-shipped signature verifier.
  • Monitor the systemd path unit for request files whose contents reference unusual verifier paths or unit names.
  • Correlate activity from the hmailserver service account UID with subsequent root-owned child processes.

Monitoring Recommendations

  • Enable Linux auditd rules on the live-update request file and the hmailserver-update binary to capture writes and executions.
  • Forward process ancestry and command-line telemetry to a centralized data lake for retrospective hunting across hosts.
  • Alert on any new privileged child process whose parent is hmailserver-update and whose binary path is not in an approved allowlist.

How to Mitigate CVE-2026-104658

Immediate Actions Required

  • Upgrade hMailServer to version 6.3.6 on all Linux hosts running 6.3.4 or 6.3.5.
  • Inventory .deb, .rpm, and AppImage deployments to confirm the live-update path unit status.
  • Restrict shell access and audit all processes running under the hmailserver service account.

Patch Information

Progressive Robot addressed the vulnerability in hMailServer 6.3.6. The fixed release is available at GitLab hMailServer Release 6.3.6. Administrators should apply vendor-provided packages rather than manually patching the helper.

Workarounds

  • Disable the live-update systemd path unit until the patched release can be deployed.
  • Remove or chmod the live-update request file path so the hmailserver service account cannot write to it.
  • Enforce mandatory access controls (SELinux or AppArmor) to prevent hmailserver-update from executing binaries outside a trusted directory.
bash
# Configuration example: disable the live-update path unit until patched
sudo systemctl disable --now hmailserver-update.path
sudo systemctl mask hmailserver-update.path

# Verify the unit is inactive
systemctl status hmailserver-update.path

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.