Skip to main content
Vulnerability Database/CVE-2026-84465

CVE-2026-84465: Zammad S/MIME Certificate Auth Bypass

CVE-2026-84465 is an authentication bypass flaw in Zammad helpdesk that allows attackers to forge S/MIME-signed emails using fake certificates. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-84465 Overview

Zammad, an open source web-based helpdesk and customer support system, contains a signature verification flaw in versions prior to 7.1.2. When Zammad processes an incoming S/MIME-signed email, it checks only whether a certificate with a matching name already exists in the system. It does not verify that the signing certificate is genuinely trusted or chains to a trusted authority. An attacker can generate a self-issued certificate using the name of a previously trusted sender and send a forged email. Zammad displays the forged message with the same "validly signed" indicator as a legitimate message, enabling identity spoofing of trusted correspondents.

Critical Impact

Attackers can forge S/MIME-signed emails that Zammad presents as validly signed from trusted senders, enabling phishing, social engineering, and fraudulent ticket creation under the identity of trusted parties.

Affected Products

  • Zammad helpdesk and customer support system
  • All versions prior to 7.1.2
  • Deployments processing inbound S/MIME-signed email

Discovery Timeline

  • 2026-09-25 - CVE-2026-84465 published to the National Vulnerability Database
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-84465

Vulnerability Analysis

The flaw is categorized as improper authentication [CWE-290]. Zammad's inbound mail processor accepts S/MIME-signed messages and attempts to validate the attached signature. The validation routine performs a name-based lookup against certificates already stored in Zammad rather than performing a full cryptographic trust chain validation. If any stored certificate matches the sender name on the incoming message, Zammad treats the message as validly signed. The verification therefore fails to distinguish between a certificate issued by a trusted certificate authority and a self-signed certificate that merely reuses the name of a known sender.

Root Cause

The root cause is the absence of trust chain and issuer validation during S/MIME signature verification. Name matching is treated as a sufficient proxy for authenticity. An attacker who knows the display name or email address of a previously trusted sender can produce a cryptographically valid signature using an attacker-controlled key pair, and Zammad will accept it.

Attack Vector

Exploitation requires only the ability to send email to a Zammad instance that has previously trusted at least one S/MIME certificate for the impersonated sender. The attacker generates an X.509 certificate carrying the target sender's name or email address, signs an arbitrary message with the matching private key, and delivers it to the Zammad mailbox. Zammad renders the ticket with the "validly signed" indicator, lending credibility to phishing content, fraudulent instructions, or malicious attachments. User interaction is required because an agent must view and act on the forged ticket.

See the GitHub Security Advisory GHSA-m9ff-hjr3-93h4 for additional detail.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-84465

Indicators of Compromise

  • Inbound S/MIME-signed emails whose signing certificate issuer is self-signed or does not chain to a recognized certificate authority.
  • Tickets displaying a valid signature indicator where the signing certificate fingerprint differs from the historical fingerprint associated with that sender.
  • Multiple certificates stored in Zammad for the same sender identity, especially recently added self-signed certificates.

Detection Strategies

  • Audit the Zammad certificate store for duplicate or recently added certificates matching known trusted sender names.
  • Compare S/MIME signature fingerprints on recent tickets against a baseline of historically used fingerprints for each sender.
  • Review mail transport logs for signed messages originating from unexpected sending infrastructure or mismatched DKIM, SPF, and DMARC results.

Monitoring Recommendations

  • Alert on creation or import of new S/MIME certificates in Zammad outside of change control windows.
  • Correlate inbound email authentication results (SPF, DKIM, DMARC) with Zammad's signature validation outcome to surface discrepancies.
  • Track agent interactions with newly received signed tickets from high-value senders for signs of social engineering follow-through.

How to Mitigate CVE-2026-84465

Immediate Actions Required

  • Upgrade Zammad to version 7.1.2 or later across all production and staging instances.
  • Review the Zammad certificate store and remove any untrusted or unexpected certificates associated with trusted senders.
  • Notify agents that prior "validly signed" indicators on historical tickets may not reflect genuine signature trust.

Patch Information

The issue is fixed in Zammad 7.1.2. The upstream fix is published in commit 9a07d0b8214ac4e8e10c23fce71d613bd0625524 and documented in the Zammad Security Advisory GHSA-m9ff-hjr3-93h4. The fix adds proper trust chain verification during S/MIME signature validation rather than relying on name matching alone.

Workarounds

  • If immediate patching is not possible, disable the display of S/MIME signature validity indicators in Zammad to prevent agents from relying on them.
  • Restrict inbound mail to Zammad using upstream gateway controls that enforce SPF, DKIM, and DMARC alignment for impersonated domains.
  • Train agents to independently verify sensitive requests from signed senders through out-of-band communication until the patch is applied.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.