Executive Summary

CVE-2026-34782 is a missing authorization vulnerability in the AI assistance controller for text tools within the Zammad helpdesk system, specifically affecting version 7.0.0.

The REST endpoint POST /api/v1/ai_assistance/text_tools/:id did not verify whether a user had the necessary privileges to use the text tool, allowing unrestricted access regardless of user permissions.

This flaw was fixed in version 7.0.1 by adding a check to ensure that only users with the ticket.agent permission can access the endpoint.

The vulnerability is classified under CWE-862 (Missing Authorization), meaning the product failed to perform an authorization check when an actor attempted to access a resource or perform an action.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows unauthorized users to access the AI assistance text tool endpoint without proper permission verification.

Because the attack vector is network-based and requires low privileges with no user interaction, an attacker could exploit this vulnerability remotely and easily.

The impact is considered moderate with a CVSS v4 base score of 5.3, primarily affecting confidentiality with low impact, and no impact on integrity or availability.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves unauthorized access to the REST endpoint POST /api/v1/ai_assistance/text_tools/:id in Zammad versions prior to 7.0.1 and 6.5.4. To detect exploitation attempts on your network or system, you can monitor HTTP POST requests targeting this specific endpoint.

For example, you can use network monitoring tools or web server logs to search for POST requests to /api/v1/ai_assistance/text_tools/ with various IDs.

• Using grep on web server access logs: grep 'POST /api/v1/ai_assistance/text_tools/' /var/log/nginx/access.log
• Using tcpdump to capture HTTP POST requests to the endpoint: tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST /api/v1/ai_assistance/text_tools/'

Additionally, you can audit user permissions and API usage logs within Zammad to identify any unauthorized usage of the text tools API.

Useful 0 Not Useful 0

Mitigation Strategies

The primary mitigation step is to upgrade Zammad to version 7.0.1 or later (or 6.5.4 or later if using the 6.5.x branch), where the authorization check for the text tools endpoint has been implemented.

Until you can upgrade, consider restricting access to the vulnerable REST endpoint by network-level controls such as firewall rules or web application firewall (WAF) rules to limit access to trusted users only.

Review and tighten user permissions within Zammad to ensure that only privileged users have access to sensitive API endpoints.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability in Zammad allows unauthorized users to access the AI assistance text tool endpoint without proper privilege checks. While the impact on confidentiality is low and there is no impact on integrity or availability, this missing authorization could potentially lead to unauthorized access to certain functionalities or data.

Such unauthorized access issues can affect compliance with standards like GDPR or HIPAA, which require strict access controls and protection of personal or sensitive data. Even though the direct confidentiality impact is low, failure to enforce proper authorization may be viewed as a compliance risk under these regulations.

Useful 0 Not Useful 0