ZA
Product
zammad
On CISA KEVExploited in the wild
123
CVEs
2
On KEV
9.8
Max CVSS
2
New 30D
Severity mix
Critical 12High 32Medium 75Low 4
Watch
Add zammad to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2020-10097 | 5.3 | Mar 5 | An issue was discovered in Zammad 3.0 through 3.2 Affected: 1.0.0 through 3.2.0 |
| CVE-2026-63208 | 5.1 | Sep 25 | Zammad: Microsoft Graph error logs expose partially masked OAuth access tokens Affected: < 7.1.2 |
| CVE-2026-63205 | 5.1 | Sep 25 | Zammad: Channel admins can read unauthorized attachments via signature rich-text body Affected: < 7.1.2 |
| CVE-2026-56726 | 5.1 | Sep 25 | Zammad: Missing authorization check in GitHub + GitLab integration allows cross-ticket data leak Affected: < 7.0.2 |
| CVE-2021-42087 | 4.9 | Oct 7 | An issue was discovered in Zammad before 4.1.1 Affected: before 4.1.1 |
| CVE-2020-29159 | 4.9 | Dec 28 | An issue was discovered in Zammad before 3.5.1 Affected: before 3.5.1 |
| CVE-2020-26028 | 4.9 | Dec 28 | An issue was discovered in Zammad before 3.4.1 Affected: 1.0.0 before 3.4.1 |
| CVE-2026-34837 | 4.3 | Apr 8 | Zammad is miissing authorization in AI assistance controller for context data used in text tools Affected: >= 7.0.0, < 7.0.1 |
| CVE-2026-34782 | 4.3 | Apr 8 | Zammad has improper access control in AI assistance controller for text tools Affected: >= 7.0.0, < 7.0.1 |
| CVE-2026-34722 | 4.3 | Apr 8 | Zammad is missing authorization in ticket create endpoint Affected: < 6.5.4; >= 7.0.0-alpha, < 7.0.1 |
| CVE-2026-34720 | 4.3 | Apr 8 | Zammad has an origin validation error in SSO mechanism Affected: < 6.5.4; >= 7.0.0-alpha, < 7.0.1 |
| CVE-2026-34719 | 4.3 | Apr 8 | Zammad has a Server-side request forgery (SSRF) via webhooks Affected: < 6.5.4; >= 7.0.0-alpha, < 7.0.1 |
| CVE-2025-32357 | 4.3 | Apr 5 | In Zammad 6.4.x before 6.4.2, an authenticated agent with knowledge base permissions was able to use the Zammad API to fetch knowledge base content that they have no permission… Affected: 6.4 before 6.4.2 |
| CVE-2024-55578 | 4.3 | Dec 9 | Zammad before 6.4.1 places sensitive data (such as auth_microsoft_office365_credentials and application_secret) in log files Affected: 6.4.0; 6.4.0 |
| CVE-2023-50457 | 4.3 | Dec 10 | An issue was discovered in Zammad before 6.2.0 Affected: 6.1.0; 6.1.0; 6.2.0 |
| CVE-2022-48023 | 4.3 | Feb 3 | Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker to perform changes on the tags of their customer tickets using the Zammad API Affected: 5.3.0 |
| CVE-2022-48022 | 4.3 | Feb 3 | An issue in the component /api/v1/mentions of Zammad v5.3.0 allows authenticated attackers with agent permissions to view information about tickets they are not authorized to see Affected: 5.3.0 |
| CVE-2022-40817 | 4.3 | Sep 27 | Zammad 5.2.1 has a fine-grained permission model that allows to configure read-only access to tickets Affected: 5.2.0 before 5.2.2 |
| CVE-2022-27331 | 4.3 | Apr 27 | An access control issue in Zammad v5.0.3 broadcasts administrative configuration changes to all users who have an active application instance, including settings that should only… Affected: before 5.1.0 |
| CVE-2021-35300 | 4.3 | Jun 28 | Text injection/Content Spoofing in 404 page in Zammad 1.0.x up to 4.0.0 could allow remote attackers to manipulate users into visiting the attackers' page Affected: 1.0.0 through 4.0.0 |
| CVE-2020-29158 | 4.3 | Dec 28 | An issue was discovered in Zammad before 3.5.1 Affected: before 3.5.1 |
| CVE-2020-26034 | 4.3 | Dec 28 | An account-enumeration issue was discovered in Zammad before 3.4.1 Affected: 1.0.0 before 3.4.1 |
| CVE-2020-26031 | 4.3 | Dec 28 | An issue was discovered in Zammad before 3.4.1 Affected: 1.0.0 before 3.4.1 |
| CVE-2020-10104 | 4.3 | Mar 5 | An issue was discovered in Zammad 3.0 through 3.2 Affected: 1.0.0 through 3.2.0 |
| CVE-2025-32358 | 4.1 | Apr 5 | In Zammad 6.4.x before 6.4.2, SSRF can occur Affected: 6.4 before 6.4.2 |