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

CVE-2026-56727: Zammad PGP Signature Auth Bypass Vulnerability

CVE-2026-56727 is an authentication bypass flaw in Zammad helpdesk system that allows attackers to forge PGP email signatures. This post explains the technical details, affected versions, security impact, 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-56727 Overview

Zammad is a web-based open source helpdesk and customer support system. CVE-2026-56727 is an authentication bypass vulnerability [CWE-287] in Zammad's inbound Pretty Good Privacy (PGP) email processing. Prior to version 7.0.2, the return value from the gpg signature verification call was silently discarded. Regardless of whether gpg reported a valid, invalid, or missing signature, the handler unconditionally wrote sign: { success: true, comment: "Good signature" } to the article's security preferences. Any sender could tamper with signed message bodies or forge signatures entirely, and Zammad would present the message as cryptographically verified. The issue is fixed in Zammad 7.0.2.

Critical Impact

Attackers can forge or tamper with PGP-signed emails and Zammad will display them as cryptographically verified, misleading agents who rely on the signature indicator for authenticity.

Affected Products

  • Zammad helpdesk and customer support system versions prior to 7.0.2
  • Deployments with the PGP integration enabled
  • All inbound PGP-signed email processing paths

Discovery Timeline

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

Technical Details for CVE-2026-56727

Vulnerability Analysis

The flaw resides in Zammad's inbound PGP email handler, specifically within lib/secure_mailing/pgp/incoming.rb. The handler invoked verified_result to run gpg --verify against the detached signature and signed data, but it discarded the method's return value. The code then unconditionally called set_article_preferences with operation: :sign and marked the signature as successfully verified.

As a result, Zammad's user interface rendered a "Good signature" label on every PGP-signed inbound email, regardless of the actual verification outcome. Agents and end users who rely on this indicator to confirm sender authenticity and message integrity would trust forged or modified content.

Root Cause

The root cause is improper authentication [CWE-287] through missing validation of a security-critical return value. The verification routine performed cryptographic work but the caller did not act on the result, breaking the trust decision in the control flow. A secondary issue in lib/secure_mailing/pgp/tool/data.rb conflated inline (opaque) PGP signatures with detached signatures, causing gpg to fail with format errors on legitimate inline-signed messages.

Attack Vector

Exploitation requires only sending an email to a Zammad instance with PGP enabled. An attacker can tamper with the body of a multipart/signed PGP email, substitute an invalid signature, or omit the signature entirely. User interaction is required in the sense that an agent must view the ticket and trust the displayed verification status.

ruby
# Patch in lib/secure_mailing/pgp/incoming.rb
     signature_part = signature_part_meta_check
     return if signature_part.nil?

-    verified_result(signature_part.body.decoded)
+    return if !verified_result(signature_part.body.decoded)

     set_article_preferences(
       operation: :sign,
# Source: https://github.com/zammad/zammad/commit/4a9dd5f8a85948c5a2f96f6479d785153aac05d7

The fix adds an early return when verified_result reports failure, preventing the article preferences from being marked as signed when verification does not succeed. A companion change in lib/secure_mailing/pgp/tool/data.rb detects inline PGP messages beginning with -----BEGIN PGP MESSAGE----- and invokes gpg --verify with only the signature file.

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-56727

Indicators of Compromise

  • Inbound ticket articles with security.sign.success = true originating from senders whose public keys are not present in the Zammad PGP keyring
  • Multipart/signed messages where the detached signature fails external re-verification but Zammad shows "Good signature"
  • Unexpected ticket responses or workflow actions taken by agents based on forged sender identity

Detection Strategies

  • Re-verify stored inbound PGP messages against the Zammad keyring using gpg --verify outside the application and compare with the stored security preferences
  • Audit application logs for signature verification events that lack a corresponding successful gpg exit status
  • Correlate ticket activity with mail transfer agent logs to identify spoofed sender domains and SPF/DKIM failures on PGP-signed inbound mail

Monitoring Recommendations

  • Monitor Zammad application and web server logs for the processing of multipart/signed and application/pgp-signature content types
  • Alert on inbound email from external domains that produces articles flagged as PGP-verified
  • Track upgrade state across all Zammad hosts to confirm the 7.0.2 patch has been applied

How to Mitigate CVE-2026-56727

Immediate Actions Required

  • Upgrade all Zammad instances to version 7.0.2 or later without delay
  • Review inbound PGP-signed tickets received before patching and treat the "Good signature" indicator as untrusted for that period
  • Notify agents that signature indicators on historical tickets may not reflect actual cryptographic verification

Patch Information

Zammad released the fix in version 7.0.2. The patch is implemented in commit 4a9dd5f8a85948c5a2f96f6479d785153aac05d7 and documented in the Zammad 7.0.2 release notes and GitHub Security Advisory GHSA-56jc-34c8-2xq4.

Workarounds

  • Disable the PGP integration in Zammad until the upgrade to 7.0.2 can be deployed
  • Instruct agents to perform out-of-band verification of PGP signatures for any security-sensitive communications
  • Restrict the acceptance of inbound email from untrusted senders at the mail gateway while the patch is pending
bash
# Verify Zammad version after upgrade
zammad run rails r 'puts Zammad::Version.get'
# Expected output: 7.0.2 or higher

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.