Description
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.
Published: 2026-09-25
Score: 5.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized disclosure of attachments
Action: Apply Patch
AI Analysis

Impact

Zammad, the open‑source helpdesk platform, processes inline images in email signatures. Prior to version 7.1.2, any referenced attachment is copied into a new signature record without verifying the user’s rights to the original file. The copy becomes downloadable by the channel‑admin creating or updating the signature, thereby exposing attachments that the admin would normally be denied access to, such as those attached to tickets in unshared groups.

Affected Systems

Installations of Zammad before version 7.1.2 that grant users the admin.channel_email, admin.channel_google, admin.channel_microsoft365, or admin.channel_microsoft_graph permissions are impacted. These users can create or modify signatures that include HTML img tags pointing to attachments owned by other groups.

Risk and Exploitability

The CVSS score of 5.1 indicates a moderate impact. Since the vulnerability involves creating or updating signatures through the web interface, it is inferred that the attack vector is internal via the web interface. No EPSS data is available, and the vulnerability is not listed in CISA KEV. Exploitation requires only the ability to create or update a signature, a privilege normally held by channel admins. By embedding image references in a signature, an attacker can read otherwise restricted attachments.

Generated by OpenCVE AI on September 25, 2026 at 20:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Zammad to version 7.1.2 or later to eliminate the attachment copy flaw.
  • Disable the ability for channel‑admins to insert custom HTML signatures until the fix is applied.
  • Restrict channel‑admin permissions to the minimal set of required rights, removing any that are not essential to managing emails.

Generated by OpenCVE AI on September 25, 2026 at 20:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 29 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 26 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
First Time appeared Zammad
Zammad zammad
Vendors & Products Zammad
Zammad zammad

Fri, 25 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Zammad: Channel admins can read unauthorized attachments via signature rich-text body
Weaknesses CWE-639
CWE-862
References
Metrics cvssV4_0

{'score': 5.1, 'vector': '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-29T19:40:34.778Z

Reserved: 2026-07-15T22:19:06.906Z

Link: CVE-2026-63205

cve-icon Vulnrichment

Updated: 2026-09-29T19:40:30.937Z

cve-icon NVD

Status : Deferred

Published: 2026-09-25T19:17:54.837

Modified: 2026-09-29T20:17:21.623

Link: CVE-2026-63205

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T10:30:09Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization