CVE-2026-84465

published 25 Sep 2026 · updated 29 Sep 2026

Zammad: S/MIME signature verification allows forged sender impersonation

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Zammad GmbHZammad<7.1.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Zammad, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-84465 severity on Zeptric[![CVE-2026-84465](https://zeptric.io/badge/cve/CVE-2026-84465.svg)](https://zeptric.io/cve/CVE-2026-84465)