Sender impersonation via certificate-name trust matching
Published Sep 25, 2026 · Updated Sep 25, 2026
Improper certificate validation in Zammad before 7.1.2 allows remote attackers to impersonate trusted senders through S/MIME-signed email. The verifier treats a certificate as trusted when its subject name matches a stored certificate, without validating the presented certificate's trust chain. Exploitation requires the name of a previously trusted sender and causes forged mail to receive the same valid-signature indicator as genuine mail.
Summary
What happened
Improper certificate validation in Zammad before 7.1.2 allows remote attackers to impersonate trusted senders through S/MIME-signed email. The verifier treats a certificate as trusted when its subject name matches a stored certificate, without validating the presented certificate's trust chain. Exploitation requires the name of a previously trusted sender and causes forged mail to receive the same valid-signature indicator as genuine mail.
The record
- CVE
- CVE-2026-84465
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- Zammad GmbH
- Product
- Zammad
- Classifications
- CWE-290, CWE-295, CWE-347, T1656
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started