Improper certificate validation in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote unauthenticated attacker to have S/MIME-encrypted mail that the account later sends to another correspondent also encrypted to the attacker's key. When its recipient opened a signed message, the webmail kept the signer's certificate for encrypting replies whether or not the server found its chain trusted, under the first e-mail address the certificate listed rather than the message's From address, and beside any certificate already held for that address. Encrypted mail later sent from the webmail to that address was encrypted to every certificate held for it, so a holder of the kept certificate's key who obtains a copy of such a message can read it.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

Upgrade to hMailServer 6.3.6, whose webmail keeps a signer's certificate only when its chain is trusted, only under the From address the signature was verified for, and a different certificate for an address that has one only when the reader chooses to. After upgrading, review the correspondents' certificates on the webmail's Security page and remove any that should not be there. Until then: check the certificates listed for an address before sending it encrypted mail from the webmail, or encrypt in a mail program.


Workaround

No workaround given by the vendor.

History

Thu, 08 Oct 2026 12:00:00 +0000

Type Values Removed Values Added
Description Improper certificate validation in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote unauthenticated attacker to have S/MIME-encrypted mail that the account later sends to another correspondent also encrypted to the attacker's key. When its recipient opened a signed message, the webmail kept the signer's certificate for encrypting replies whether or not the server found its chain trusted, under the first e-mail address the certificate listed rather than the message's From address, and beside any certificate already held for that address. Encrypted mail later sent from the webmail to that address was encrypted to every certificate held for it, so a holder of the kept certificate's key who obtains a copy of such a message can read it.
Title Improper Certificate Validation in hMailServer
Weaknesses CWE-295
References
Metrics cvssV3_1

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


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-10-08T11:49:01.081Z

Reserved: 2026-10-08T11:17:47.802Z

Link: CVE-2026-107587

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-08T12:17:16.937

Modified: 2026-10-08T12:17:16.937

Link: CVE-2026-107587

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses