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-84460 Overview
Zammad is a web-based open source helpdesk and customer support system. A broken access control flaw [CWE-639] in versions prior to 7.1.2 allows any authenticated user to query the REST endpoint that returns a ticket's tag list, even without authorization to view the ticket itself. Because ticket IDs are sequential integers, an attacker can enumerate the full ticket space and harvest tag names at scale. Tags are an internal categorization feature and may expose sensitive labels such as customer identifiers, product codenames, or incident classifications. The maintainers resolved the issue in Zammad 7.1.2.
Critical Impact
Authenticated users can enumerate tag metadata for every ticket in a Zammad instance, exposing sensitive internal categorizations without triggering standard ticket access controls.
Affected Products
- Zammad helpdesk and customer support system versions prior to 7.1.2
- Zammad REST tag listing endpoint (tags controller)
- Zammad GraphQL AutocompleteSearch::Tag query
Discovery Timeline
- 2026-09-25 - CVE-2026-84460 published to the National Vulnerability Database
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-84460
Vulnerability Analysis
The vulnerability is an Insecure Direct Object Reference (IDOR) in the Zammad tags API. The server-side policy for the tag listing action evaluated to true unconditionally, meaning any authenticated session could request tags for an arbitrary ticket ID. The REST endpoint returned the tag names associated with the referenced ticket without first checking whether the requesting user had read permission on that ticket. A parallel issue affected the AutocompleteSearch::Tag GraphQL query, which lacked permission guards and exposed the full tag namespace to any authenticated caller.
Root Cause
The root cause is a missing authorization check in app/policies/controllers/tags_controller_policy.rb. The list? policy method returned true for every authenticated principal rather than delegating to an ownership or read-access check on the underlying ticket. Zammad fixed this by binding list? to object_read?, which enforces that the caller has read access to the tagged object. A follow-up commit also restricted the tag search? action to users holding ticket.agent, admin.tag, or knowledge_base.editor permissions.
Attack Vector
An attacker needs only valid low-privileged credentials for the target Zammad instance. Because ticket identifiers are sequential integers, the attacker iterates from 1 upward and issues a tag list request for each ID. The response reveals tag names regardless of ticket ownership, enabling bulk reconstruction of internal taxonomies and selective targeting of tickets with sensitive labels.
# Patch 1: app/policies/controllers/tags_controller_policy.rb
# Replace unconditional authorization with an object-level read check.
def list?
- true
+ object_read?
end
Source: Zammad commit d1a5eabd
# Patch 2: app/policies/controllers/tags_controller_policy.rb
# Restrict tag search to privileged roles only.
def search?
- true
+ user.permissions?(['ticket.agent', 'admin.tag', 'knowledge_base.editor'])
end
# Patch 3: app/graphql/gql/queries/autocomplete_search/tag.rb
# Require explicit permissions on the tag autocomplete GraphQL query.
module Gql::Queries
class AutocompleteSearch::Tag < BaseQuery
+ requires_permission 'ticket.agent', 'admin.tag', 'knowledge_base.editor'
description 'Search for tags'
Source: Zammad commit 13217eb6
Detection Methods for CVE-2026-84460
Indicators of Compromise
- Sequential GET requests against the tags listing endpoint iterating ticket IDs (for example, /api/v1/tags?object=Ticket&o_id=1, o_id=2, o_id=3).
- Single authenticated session issuing a high volume of tag list calls in a short interval.
- Requests to the tag listing endpoint originating from accounts that have little or no prior ticket read activity.
Detection Strategies
- Correlate Zammad application logs against ticket authorization events to flag tag list responses returned to users who lack read access on the referenced ticket.
- Deploy a web application firewall rule that alerts when any single session enumerates more than a threshold of distinct o_id values against the tags endpoint.
- Hunt in historical logs for GET /api/v1/tags and GraphQL AutocompleteSearch::Tag operations issued by non-agent accounts.
Monitoring Recommendations
- Centralize Zammad production.log and reverse proxy access logs in your SIEM for retrospective enumeration analysis.
- Baseline normal tag API usage per role and alert on deviations, particularly from customer-tier accounts.
- Monitor for failed and successful authentications followed by rapid API traversal patterns consistent with scripted enumeration.
How to Mitigate CVE-2026-84460
Immediate Actions Required
- Upgrade all Zammad instances to version 7.1.2 or later without delay.
- Review audit logs for anomalous access to the tags endpoint and the AutocompleteSearch::Tag GraphQL query since deployment.
- Rotate or re-scope tags that encode sensitive identifiers if enumeration is suspected.
- Reassess the role assignments of any non-agent accounts that have accessed the tags API.
Patch Information
The fix is included in Zammad 7.1.2. The relevant commits add an object-level read check to the list? policy method and require ticket.agent, admin.tag, or knowledge_base.editor permissions on the tag search action and the GraphQL autocomplete query. See the GitHub Security Advisory GHSA-6vgm-xxp4-p6jv for the vendor's full disclosure.
Workarounds
- No official workaround exists; upgrading to 7.1.2 is the supported remediation.
- As a temporary compensating control, restrict access to /api/v1/tags and the GraphQL endpoint at the reverse proxy to trusted internal roles until patching completes.
- Limit the issuance of authenticated Zammad accounts to only required users and enforce strong authentication to reduce the pool of potential enumerators.
# Example nginx compensating control: restrict the tags endpoint by source network
# until the Zammad upgrade to 7.1.2 is deployed.
location /api/v1/tags {
allow 10.0.0.0/8; # internal agent network
deny all;
proxy_pass http://zammad_upstream;
}
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

