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

CVE-2026-107587: hMailServer Certificate Validation Flaw

CVE-2026-107587 is an information disclosure vulnerability in Progressive Robot hMailServer webmail that allows attackers to decrypt S/MIME-encrypted messages through improper certificate validation. This article covers technical details, affected versions from 6.3.2 to 6.3.5, security impact, and recommended mitigation strategies.

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

CVE-2026-107587 is an improper certificate validation flaw [CWE-295] in the webmail component of Progressive Robot hMailServer versions 6.3.2 through 6.3.5. The webmail stores a signer's S/MIME certificate from any received signed message, regardless of whether the certificate chain is trusted. It also indexes the certificate by the first email address listed in the certificate rather than by the message's From address. Subsequent encrypted replies from the account are then encrypted to every stored certificate for that recipient, including an attacker-controlled key.

Critical Impact

A remote unauthenticated attacker who later obtains ciphertext of a victim's outbound S/MIME message can decrypt it using the key tied to the planted certificate.

Affected Products

  • Progressive Robot hMailServer 6.3.2 (webmail)
  • Progressive Robot hMailServer 6.3.3, 6.3.4 (webmail)
  • Progressive Robot hMailServer 6.3.5 (webmail)

Discovery Timeline

  • 2026-10-08 - CVE-2026-107587 published to NVD
  • 2026-10-08 - Last updated in NVD database

Technical Details for CVE-2026-107587

Vulnerability Analysis

The hMailServer webmail accepts S/MIME-signed messages and persists the signing certificate for later use when encrypting replies. Three design errors combine to create the exposure. First, the webmail retains the certificate even when the server cannot build a trusted chain. Second, it keys the certificate by the first email address embedded in the certificate's subject or subjectAltName rather than by the sender address in the message header. Third, it stores the newly received certificate alongside any existing certificate for that address instead of replacing or prompting for user review.

When the account later sends an encrypted message to that recipient, the webmail encrypts the message to every certificate it holds for the address. The attacker's certificate is one of those recipients, so the ciphertext becomes decryptable by the attacker's private key. The attack is passive from the victim's perspective and requires only that the victim open the attacker's signed message and later send encrypted mail to the same address.

Root Cause

The root cause is improper certificate validation combined with weak binding between a certificate and its email identity. The webmail trusts attacker-supplied certificates for recipient-key lookup without verifying chain of trust or confirming that the asserted email address matches the message sender.

Attack Vector

Exploitation requires network delivery of a crafted S/MIME-signed email and user interaction to open the message. The attacker crafts a certificate that lists the target correspondent's email address first in its identity fields, signs a message with it, and sends it to the victim. User interaction is required to open the signed message, and the attack succeeds only when the victim later sends an encrypted message to that correspondent and the attacker captures the ciphertext in transit or at rest.

No verified public exploit code is available. See the GitLab hMailServer Work Item #66 for maintainer discussion.

Detection Methods for CVE-2026-107587

Indicators of Compromise

  • Received S/MIME-signed messages where the signing certificate chain fails validation but is nonetheless accepted by webmail.
  • Stored webmail certificates whose first listed email address does not match the From header of the originating message.
  • Multiple distinct S/MIME certificates persisted for a single correspondent address in the webmail certificate store.

Detection Strategies

  • Audit the hMailServer webmail certificate store for duplicate certificates mapped to the same recipient address.
  • Inspect outbound S/MIME messages and compare the enveloped-recipient key identifiers against expected correspondent certificates.
  • Flag any accepted S/MIME certificate whose issuer chain terminates outside the organization's trusted roots.

Monitoring Recommendations

  • Enable SMTP and webmail transaction logging and forward events to a central SIEM for correlation with certificate-store changes.
  • Monitor hMailServer upgrades to confirm all webmail instances have moved to the patched release.
  • Alert on signed inbound mail from previously unseen signer certificates addressed to users who frequently exchange encrypted mail.

How to Mitigate CVE-2026-107587

Immediate Actions Required

  • Upgrade hMailServer webmail to version 6.3.6 or later as published in the GitLab hMailServer Release v6.3.6.
  • Review the webmail certificate store and remove untrusted or unexpected S/MIME certificates for all accounts.
  • Instruct users to avoid opening S/MIME-signed messages from unknown senders until the patch is deployed.

Patch Information

Progressive Robot addressed this issue in hMailServer release v6.3.6. Administrators should deploy the upgrade across all webmail instances and verify that the certificate-handling logic enforces chain validation and binds certificates to the message From address.

Workarounds

  • Disable S/MIME encryption and signature processing in webmail until the patched release is installed.
  • Restrict webmail access to trusted networks to reduce exposure to unsolicited signed messages.
  • Educate users to delete rather than open signed mail from unverified senders during the mitigation window.

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.