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

CVE-2026-56730: Zammad Authorization Bypass Vulnerability

CVE-2026-56730 is an authorization bypass flaw in Zammad helpdesk system that allows authenticated agents to access unauthorized knowledge base content. 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-56730 Overview

CVE-2026-56730 is an authorization bypass vulnerability in Zammad, a web-based open source helpdesk and customer support system. Versions prior to 7.0.2 allow an authenticated agent to read knowledge base answer content they should not be able to access. The vulnerable GraphQL mutation transforms a knowledge base answer suggestion for insertion into the ticket editor. It only validates the ticket.agent permission and omits the authorization check against the knowledge base answer itself. The issue is tracked as [CWE-862: Missing Authorization] and is fixed in Zammad 7.0.2.

Critical Impact

Any authenticated agent can retrieve restricted knowledge base answer content by invoking the transform mutation with a target translation identifier.

Affected Products

  • Zammad versions prior to 7.0.2
  • Zammad GraphQL API — knowledgeBaseAnswerSuggestionContentTransform mutation
  • Deployments exposing agent-level accounts to the Zammad web interface

Discovery Timeline

Technical Details for CVE-2026-56730

Vulnerability Analysis

Zammad exposes a GraphQL mutation that converts a knowledge base answer suggestion into content suitable for the ticket editor. The resolver in app/graphql/gql/mutations/knowledge_base/answer/suggestion/content/transform.rb enforces only a coarse-grained role check through requires_permission 'ticket.agent'. It then resolves the supplied translation_id using Gql::ZammadSchema.verified_object_from_id, which validates the object type but does not evaluate per-object authorization. As a result, any authenticated agent can pass a translation_id for a knowledge base answer outside their permitted scope and receive the transformed body in the mutation response. The flaw is a horizontal authorization bypass against knowledge base content, categorized under [CWE-862].

Root Cause

The root cause is a missing object-level authorization check. The resolver conflated role possession (ticket.agent) with permission to read a specific KnowledgeBase::Answer::Translation. Zammad's policy framework was never consulted for the target object.

Attack Vector

An attacker needs valid agent credentials and network access to the Zammad GraphQL endpoint. They enumerate or guess translation identifiers and invoke the transform mutation. The mutation returns the answer body regardless of whether the agent should have access to that knowledge base category.

ruby
     requires_permission 'ticket.agent'
 
     def resolve(translation_id:, form_id:)
-      translation = Gql::ZammadSchema.verified_object_from_id(translation_id, type: ::KnowledgeBase::Answer::Translation)
+      translation = Gql::ZammadSchema.authorized_object_from_id(translation_id, type: ::KnowledgeBase::Answer::Translation, user: context.current_user)
 
       {
         body:        convert_body(translation, form_id),

Source: Zammad commit b059bd1. The patch replaces verified_object_from_id with authorized_object_from_id, which evaluates the current user's permission against the target translation before returning it.

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

Indicators of Compromise

  • GraphQL requests targeting the knowledgeBaseAnswerSuggestionContentTransform mutation from agents who do not own or interact with related tickets
  • Repeated mutation invocations enumerating sequential or varied translation_id values from a single session
  • Mutation responses returning knowledge base bodies to agents without matching role permissions for the source category

Detection Strategies

  • Parse Zammad application logs and the GraphQL request log to flag transform mutation calls that do not correlate with an active ticket composition event in the same session
  • Correlate agent accounts, source IP, and the volume of knowledge base translation IDs accessed per time window to identify enumeration patterns
  • Alert on mutation invocations by accounts outside the business groups normally permitted to view the referenced knowledge base category

Monitoring Recommendations

  • Enable verbose GraphQL request logging in Zammad and forward it to a central SIEM for retention and query
  • Baseline normal agent usage of knowledge base suggestions, then alert on deviations exceeding the baseline
  • Review audit records of agent accounts after upgrading to confirm whether suspect queries occurred prior to patching

How to Mitigate CVE-2026-56730

Immediate Actions Required

  • Upgrade all Zammad instances to version 7.0.2 or later without delay
  • Audit agent accounts and revoke ticket.agent from users who no longer require it
  • Review GraphQL access logs for prior invocations of the vulnerable transform mutation and assess data exposure

Patch Information

The fix is available in Zammad 7.0.2 and documented in GHSA-pf47-8964-pp23. The code change is captured in commit b059bd1, which swaps verified_object_from_id for authorized_object_from_id so the resolver enforces per-object authorization using Zammad's Pundit policies.

Workarounds

  • No vendor-supplied workaround exists; upgrading to 7.0.2 is required
  • As a temporary compensating control, restrict the agent role to trusted users and reduce the number of accounts with ticket.agent until the patch is applied
  • Place the Zammad GraphQL endpoint behind an authenticated reverse proxy that logs and rate-limits mutation traffic
bash
# Upgrade Zammad to the patched release using the official package repository
# Debian/Ubuntu example
sudo apt-get update
sudo apt-get install --only-upgrade zammad

# Verify installed version is 7.0.2 or later
zammad run rails runner 'puts Zammad::Version.get'

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.