CVE-2026-34837 | Zammad up to 7.0.0 REST Endpoint :id authorization
VulDBArchived Apr 08, 2026✓ Full text saved
A vulnerability categorized as problematic has been discovered in Zammad up to 7.0.0 . This affects an unknown function of the file /api/v1/ai_assistance/text_tools/:id of the component REST Endpoint . The manipulation results in missing authorization. This vulnerability is cataloged as CVE-2026-34837 . The attack may be launched remotely. There is no exploit available. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-356365 · CVE-2026-34837 · GCVE-0-2026-34837
ZAMMAD UP TO 7.0.0 REST ENDPOINT :ID AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.1 $0-$5k 0.65
Summaryinfo
A vulnerability identified as problematic has been detected in Zammad up to 7.0.0. This impacts an unknown function of the file /api/v1/ai_assistance/text_tools/:id of the component REST Endpoint. This manipulation causes authorization. This vulnerability is registered as CVE-2026-34837. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Detailsinfo
A vulnerability classified as problematic was found in Zammad up to 7.0.0. Affected by this vulnerability is some unknown functionality of the file /api/v1/ai_assistance/text_tools/:id of the component REST Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. The summary by CVE is:
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1, he REST endpoint POST /api/v1/ai_assistance/text_tools/:id contains an authorization failure. Context data (e.g., a group or organization) supplied to be used in the AI prompt were not checked if they are accessible for the current user. This leads to having data present in the AI prompt that were not authorized before being used. A user needs to have ticket.agent permission to be able to use the provided context data. This vulnerability is fixed in 7.0.1.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-34837 since 03/30/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
Upgrading to version 7.0.1 eliminates this vulnerability.
Productinfo
Name
Zammad
Version
7.0
License
open-source
Website
Product: https://github.com/zammad/zammad/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Zammad 7.0.1
Timelineinfo
03/30/2026 CVE reserved
04/08/2026 +9 days Advisory disclosed
04/08/2026 +0 days VulDB entry created
04/08/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-34837 (🔒)
GCVE (CVE): GCVE-0-2026-34837
GCVE (VulDB): GCVE-100-356365
Entryinfo
Created: 04/08/2026 21:10
Changes: 04/08/2026 21:10 (66)
Complete: 🔍
Cache ID: 99:B44:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸