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

CVE-2026-56723: Zammad Auth Bypass Vulnerability

CVE-2026-56723 is an authorization bypass flaw in Zammad that allows customers to download internal ticket attachments without proper authorization. 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-56723 Overview

CVE-2026-56723 is a broken access control vulnerability in Zammad, a web-based open source helpdesk and customer support system. Versions prior to 7.0.2 fail to enforce article-level authorization on the attachment download endpoint. The article listing API correctly hides internal articles from customers who can view a ticket. However, the attachment download endpoint only validates access to the parent ticket, not the specific article. A customer with legitimate ticket access can directly request attachment identifiers from internal articles and retrieve their contents. The flaw is categorized under [CWE-863: Incorrect Authorization] and is fixed in Zammad 7.0.2.

Critical Impact

Authenticated customers can download attachments from internal helpdesk articles that were intended to remain invisible to them, exposing confidential agent notes and internal correspondence.

Affected Products

  • Zammad helpdesk and customer support platform
  • All Zammad releases prior to version 7.0.2
  • Both self-hosted and container-based Zammad deployments

Discovery Timeline

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

Technical Details for CVE-2026-56723

Vulnerability Analysis

The vulnerability resides in Zammad's ticket articles controller, which handles attachment downloads. The listing endpoint for ticket articles correctly filters out internal articles when the requester is a customer. The attachment download endpoint, however, performs only a ticket-level authorization check. It calls authorize!(ticket, :show?) before serving the file and does not validate that the requester can view the parent article. A customer who already has ticket visibility can enumerate or guess attachment identifiers and fetch files that belong to internal-only articles. Exposed content commonly includes agent-to-agent notes, screenshots of internal systems, support escalation records, and customer data shared only between staff.

Root Cause

The root cause is inconsistent authorization enforcement between two related endpoints. The article listing applied article-level visibility filtering, but the attachment download assumed the parent ticket check was sufficient. This mismatch is a classic [CWE-863] broken access control pattern where authorization logic diverges across adjacent endpoints that handle the same underlying resource hierarchy.

Attack Vector

Exploitation requires network access to the Zammad instance and valid customer credentials with view access to a ticket that contains internal articles with attachments. The attacker issues an authenticated HTTP request to the attachment download route using the attachment identifier associated with an internal article. No user interaction, elevated privileges, or specialized tooling is required beyond standard API access.

ruby
# Patch applied in app/controllers/ticket_articles_controller.rb
       authorize!(ticket, :show?)
     end
 
+    authorize!(article, :show?)
+
     list = article.attachments || []
     access = false
     list.each do |item|

Source: GitHub commit e661d00. The fix adds an explicit authorize!(article, :show?) call so Pundit enforces article-level visibility before the controller enumerates attachments.

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

Indicators of Compromise

  • Authenticated requests to attachment download routes under /api/v1/ticket_attachment/ originating from customer-role accounts.
  • Attachment downloads by a customer where the referenced article was never returned in that user's prior article listing responses for the same ticket.
  • Sequential or enumerated attachment identifier access patterns from a single customer session.

Detection Strategies

  • Correlate article listing responses with subsequent attachment downloads per session, and flag downloads of attachment IDs that were not disclosed in the listing.
  • Monitor Zammad application logs for TicketArticlesController attachment actions where the acting user has the customer role.
  • Compare the internal flag on parent articles against the role of the downloading user in the audit trail.

Monitoring Recommendations

  • Ship Zammad Rails and web server logs to a centralized log platform for retention and query.
  • Alert on spikes in attachment download volume per customer account, which may indicate enumeration.
  • Baseline normal customer access patterns against tickets and investigate deviations such as downloads referencing internal-only article IDs.

How to Mitigate CVE-2026-56723

Immediate Actions Required

  • Upgrade all Zammad instances to version 7.0.2 or later without delay.
  • Review Zammad access logs since the deployment of affected versions for suspicious attachment download activity by customer accounts.
  • Audit internal articles containing sensitive attachments and rotate any credentials, tokens, or secrets that may have been exposed.

Patch Information

The fix is included in Zammad 7.0.2. The patch adds an authorize!(article, :show?) call in the attachment download path within app/controllers/ticket_articles_controller.rb. Technical details are documented in GitHub Security Advisory GHSA-374g-4f73-g7m7.

Workarounds

  • No official workaround exists; upgrading to 7.0.2 is the supported remediation.
  • As an interim measure, restrict customer access to tickets that contain internal articles with sensitive attachments until the upgrade is applied.
  • Remove or re-upload sensitive attachments on affected tickets as non-internal, access-controlled resources only after patching.
bash
# Upgrade Zammad to the patched release
# Debian/Ubuntu package-based installation
sudo apt-get update
sudo apt-get install --only-upgrade zammad

# Docker Compose deployment
docker compose pull
docker compose up -d

# Verify the installed version is 7.0.2 or later
zammad run rails r 'puts Zammad::VERSION::STRING'

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.