CVE-2026-63205
- Source
- https://cve.org/CVERecord?id=CVE-2026-63205
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-63205.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-63205
- Aliases
-
- GHSA-pp8r-x7pp-5qj5
- Published
- 2026-09-25T18:13:25Z
- Modified
- 2026-09-26T03:47:03Z
- Severity
-
- 5.1 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Zammad: Channel admins can read unauthorized attachments via signature rich-text body
- Details
-
Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when creating or updating an email signature, Zammad processes inline images referenced in the signature body. If a signature body contains an HTML img tag pointing to any existing attachment, the system copies that attachment into a new signature-owned record, without checking whether the user has permission to access the original attachment. The newly created copy is then downloadable by the same channel-admin user, because attachment access is determined by the copy's owner (the signature), not the original object (e.g., a ticket or knowledge-base article). This allows a user with any of the admin.channel_email, admin.channel_google, admin.channel_microsoft365, or admin.channel_microsoft_graph permissions to read attachments they would otherwise be denied access to, such as ticket attachments belonging to groups they are not a member of. This issue is fixed in version 7.1.2.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-639", "CWE-862" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63205.json" }- References