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

CVE-2026-56728: Zammad GraphQL API Access Control Vulnerability

CVE-2026-56728 is an information disclosure vulnerability in Zammad's GraphQL API that allows authenticated users to access other users' taskbar data. This article covers the technical details, affected versions, and mitigation.

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-56728 Overview

CVE-2026-56728 is a broken access control vulnerability in Zammad, a web-based open source helpdesk and customer support system. The flaw resides in Zammad's GraphQL API, where the authorization check for taskbar item access is not consistently enforced. An authenticated user can craft a request containing another user's taskbar identifier and read taskbar item data belonging to that user. The taskbar feature stores transient session state, including auto-saved ticket drafts, which may contain sensitive customer or operational information. The issue affects Zammad versions prior to 7.0.2 and is fixed in release 7.0.2. The weakness is classified under [CWE-200] (Exposure of Sensitive Information to an Unauthorized Actor).

Critical Impact

Authenticated Zammad users can read other users' taskbar item data, including auto-saved ticket drafts, by referencing a target taskbar identifier via the GraphQL API.

Affected Products

  • Zammad versions prior to 7.0.2
  • Zammad GraphQL API taskbar item mutations and queries
  • Self-hosted and containerized Zammad deployments running vulnerable versions

Discovery Timeline

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

Technical Details for CVE-2026-56728

Vulnerability Analysis

The vulnerability exists in Zammad's GraphQL mutations that operate on taskbar items of the currently logged-in user. The mutation handlers load a TaskbarItemType object by its ID argument but do not run the appropriate Pundit authorization policy against the loaded record. As a result, the loader resolves any taskbar item whose ID is supplied by the caller, regardless of ownership.

Taskbar items store transient state for active user sessions, including auto-saved ticket drafts. An attacker who holds a valid Zammad account can therefore query or mutate another user's draft content, exposing in-progress ticket responses, internal notes, or customer identifiers held in draft form.

Root Cause

The root cause is a missing object-level authorization check on GraphQL arguments that use the loads: option to resolve TaskbarItemType. Without binding a Pundit method such as destroy? or update? to the loader, GraphQL-Ruby's object resolution bypasses per-record policy enforcement and returns the record whenever the ID matches.

Attack Vector

Exploitation requires an authenticated session with low privileges. The attacker enumerates or obtains a target user's taskbar item ID and issues a GraphQL mutation referencing that ID. The server loads the record and executes the operation in the attacker's context, returning or modifying data owned by the victim. No user interaction from the victim is required.

ruby
# Patch excerpt: app/graphql/gql/mutations/user/current/taskbar_item/delete.rb

    description 'Delete a taskbar item of the currently logged-in user'

-    argument :id, GraphQL::Types::ID, required: true, loads: Gql::Types::User::TaskbarItemType, as: :taskbar_item, description: 'The taskbar item ID'
+    argument :id, GraphQL::Types::ID, required: true, loads: Gql::Types::User::TaskbarItemType, as: :taskbar_item, loads_pundit_method: :destroy?, description: 'The taskbar item ID'

    field :success, Boolean, description: 'This indicates if deleting the user (session) device was successful.'

Source: Zammad commit 4ccd5d5

The patch binds the Pundit destroy? policy to the loader so Zammad verifies the caller is permitted to act on the referenced taskbar item. A parallel change applies update? to the touch_last_contact mutation.

ruby
# Patch excerpt: app/graphql/gql/mutations/user/current/taskbar_item/touch_last_contact.rb

    description 'Update last_contact_at for a taskbar item of the currently logged-in user'

-    argument :id, GraphQL::Types::ID, required: true, loads: Gql::Types::User::TaskbarItemType, as: :taskbar_item, description: 'The taskbar item ID'
+    argument :id, GraphQL::Types::ID, required: true, loads: Gql::Types::User::TaskbarItemType, as: :taskbar_item, loads_pundit_method: :update?, description: 'The taskbar item ID'

    field :taskbar_item, Gql::Types::User::TaskbarItemType, description: 'The updated taskbar item.'

Source: Zammad commit 4ccd5d5

Detection Methods for CVE-2026-56728

Indicators of Compromise

  • GraphQL mutations targeting taskbarItemDelete or taskbarItemTouchLastContact where the referenced taskbar item ID does not belong to the authenticated session user.
  • Unexpected deletions or last_contact_at updates on taskbar items in the taskbars database table that do not correlate with the owning user's recent activity.
  • Anomalous volume of GraphQL requests from a single account enumerating sequential or guessed taskbar IDs.

Detection Strategies

  • Enable GraphQL request logging on the Zammad Rails backend and alert on taskbar item operations where the request user ID differs from the resolved record's user_id.
  • Correlate web server access logs with Zammad audit records to identify accounts issuing taskbar mutations against IDs they have never created.
  • Review Pundit authorization failures introduced after upgrading to 7.0.2 to retroactively identify prior probing attempts in historical logs.

Monitoring Recommendations

  • Monitor the /graphql endpoint for high-rate requests from authenticated agents and surface outliers for review.
  • Track row-level changes in the taskbars table and alert when records are modified by a session that does not match the row owner.
  • Forward Zammad application logs into a centralized log platform and build dashboards for GraphQL mutation activity segmented by user role.

How to Mitigate CVE-2026-56728

Immediate Actions Required

  • Upgrade Zammad to version 7.0.2 or later on all production and staging deployments.
  • Audit recent taskbar item activity for cross-user access patterns and notify affected agents of potential draft exposure.
  • Rotate any sensitive credentials or customer data that may have been pasted into ticket drafts during the exposure window.

Patch Information

The fix is included in Zammad 7.0.2 and is implemented in commit 4ccd5d5. Full remediation details are documented in GitHub Security Advisory GHSA-jvcg-5539-vvc3. The patch applies loads_pundit_method: :destroy? and loads_pundit_method: :update? to the affected GraphQL arguments so ownership is enforced on each request.

Workarounds

  • If upgrading is not immediately possible, restrict Zammad access to trusted agent accounts and reduce the number of users with API privileges.
  • Place the Zammad GraphQL endpoint behind a reverse proxy or WAF rule set that rate-limits authenticated requests and blocks anomalous mutation volumes.
  • Disable or minimize use of the taskbar auto-save feature for sensitive queues until the patched version is deployed.
bash
# Verify the installed Zammad version and upgrade via package manager
zammad run rails r 'puts Version.get'

# Debian/Ubuntu example
sudo apt-get update && sudo apt-get install --only-upgrade zammad

# Docker Compose example
docker compose pull && docker compose up -d

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.