High severity · published Sep 25, 2026
CVE-2026-84465
Zammad: S/MIME signature verification allows forged sender impersonation
7.1
CVSS
0.1%
EPSS
No
On KEV
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 2% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
ZA
zammad · zammad
< 7.1.2 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-84465
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-84465
x_refsource_CONFIRM
https://github.com/zammad/zammad/security/advisories/GHSA-m9ff-hjr3-93h4
x_refsource_MISC
https://github.com/zammad/zammad/commit/9a07d0b8214ac4e8e10c23fce71d613bd0625524
More from zammad
9.8
CVE-2026-102489
Undisclosed RCE in Zammad v6.3 and higher
7.8
CVE-2026-102490
Local privilege escalation in Zammad v1.5.0 to v7.2.2 installed via DEB or RPM package
9.8
CVE-2022-48021
A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server
9.8
CVE-2022-35490
Zammad 5.2.0 is vulnerable to privilege escalation
9.8
CVE-2021-42090
An issue was discovered in Zammad before 4.1.1
