CVE-2026-84465

Zammad: S/MIME signature verification allows forged sender impersonation

State
Published
Severity
7.1 High
Published
Sep 25, 2026
Updated
Sep 29, 2026
Reserved
Sep 1, 2026

Read the record on cve.org

Description

Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when Zammad checks the digital signature on an incoming S/MIME-signed email, it does not verify that the signing certificate is genuinely trusted, it only checks whether a certificate with a matching name is already stored in the system. An attacker can create their own certificate using the name of a real, previously trusted sender and use it to send a forged email. Zammad will display that email with the same "validly signed" indicator as a genuine message from the real sender, even though the attacker never had access to that sender's actual certificate or private key. This issue is fixed in version 7.1.2.

Scores

CVSSScoreVectorSource
4.07.1 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-290 Authentication Bypass by Spoofing
  • CWE-295 Improper Certificate Validation
  • CWE-347 Improper Verification of Cryptographic Signature

Affected Products

ProductVersions
zammadzammad
  • < 7.1.2Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.