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-56729 Overview
Zammad is a web-based open source helpdesk and customer support system. CVE-2026-56729 is an information disclosure vulnerability [CWE-200] affecting Zammad versions prior to 7.0.2. When multiple Knowledge Base (KB) categories have different editor roles assigned, a user holding knowledge_base.editor permission in one category can view answer titles and updated_at timestamps from categories where they lack editor access. The leak occurs through the global quick search. Category names remain hidden, and opening the answer returns a Page not found response, but exposed titles alone may disclose sensitive information. The issue is fixed in Zammad 7.0.2.
Critical Impact
Authenticated KB editors can enumerate answer titles and modification timestamps across Knowledge Base categories they are not authorized to access, potentially exposing sensitive internal documentation metadata.
Affected Products
- Zammad versions prior to 7.0.2
- Zammad Knowledge Base module with granular category permissions
- Deployments assigning knowledge_base.editor role across multiple KB categories
Discovery Timeline
- 2026-09-25 - CVE-2026-56729 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-56729
Vulnerability Analysis
The vulnerability resides in the Knowledge Base answer translation search scope. Zammad implements granular permissions allowing different editor roles per KB category. However, the search backend applied a short-circuit check: any user holding the global knowledge_base.editor permission bypassed the per-category answer filter entirely.
As a result, the global quick search returned matching answer titles and updated_at fields from categories outside the user's authorized scope. Follow-up access to the full answer page was still blocked and returned Page not found, but the leaked title metadata alone can disclose sensitive context such as incident names, customer identifiers, or internal project references.
Root Cause
The root cause is a permission check that treated the knowledge_base.editor role as a global authorization rather than a per-category one. In app/models/knowledge_base/answer/translation/search.rb, the search_sql_extension scope returned early for any editor, skipping the category-aware search_answer_ids_for_user filter that enforces granular access.
Attack Vector
An authenticated attacker with knowledge_base.editor permission on at least one category issues targeted keyword queries through the global quick search. The response includes answer titles and timestamps from categories the attacker cannot otherwise read, enabling metadata enumeration without triggering access-denied errors on the search endpoint itself.
# Patch in app/models/knowledge_base/answer/translation/search.rb
included do
scope :search_sql_extension, lambda { |params|
- return if params[:current_user]&.permissions?('knowledge_base.editor')
-
where(answer_id: search_answer_ids_for_user(params[:current_user]))
}
Source: Zammad Commit 5076aa1
The fix removes the early return so that search_answer_ids_for_user consistently filters results against the user's category-level permissions.
Detection Methods for CVE-2026-56729
Indicators of Compromise
- Elevated global quick search query volume from accounts holding knowledge_base.editor on a limited set of categories.
- Search activity returning answer titles followed by HTTP 404 Page not found responses when the same user requests the full answer URL.
- Repeated keyword probing patterns in web access logs targeting the KB search endpoint.
Detection Strategies
- Correlate KB search requests with subsequent answer-view requests and flag users who search broadly but are blocked from opening results.
- Baseline normal search behavior per editor role and alert on users whose matched answer IDs span categories outside their assigned permissions.
- Audit the Rails application logs for search_sql_extension scope execution patterns tied to users with scoped KB roles.
Monitoring Recommendations
- Enable verbose logging on the Zammad Knowledge Base search endpoint, including user ID, query string, and returned answer IDs.
- Ship application and web access logs to a centralized analytics platform and build dashboards for cross-category search anomalies.
- Review role assignments periodically to confirm knowledge_base.editor is granted only where required.
How to Mitigate CVE-2026-56729
Immediate Actions Required
- Upgrade all Zammad instances to version 7.0.2 or later.
- Audit accounts holding knowledge_base.editor and remove unnecessary assignments.
- Review KB answer titles for sensitive content and rename entries that leak confidential context through the title alone.
Patch Information
The fix is distributed in Zammad 7.0.2. The commits removing the permission short-circuit in search_sql_extension are available in the Zammad repository: Commit 5076aa1, Commit 7b6c0ad, and Commit de5dc41. Full disclosure is published in GitHub Security Advisory GHSA-4m54-p3mr-22g2.
Workarounds
- Where upgrade is delayed, consolidate KB editor permissions so that affected users already have access to all categories, eliminating the disclosure boundary.
- Temporarily move sensitive KB answers into standalone instances or restrict them to roles that do not carry knowledge_base.editor.
- Rename sensitive answer titles to remove identifying information until the patch is applied.
# Upgrade Zammad to the fixed release
# Docker Compose example
docker compose pull
docker compose up -d
# Package-based install (Debian/Ubuntu)
sudo apt update
sudo apt install --only-upgrade zammad
# Verify installed version
zammad run rails r 'puts Version.get'
# Expected output: 7.0.2 or later
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

