Is CVE-2026-63205 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63205 being exploited in the wild.

How severe is CVE-2026-63205?

Informational severity, published 25 September 2026.

Is there a fix for CVE-2026-63205?

A patch was published on 2026-08-04: Version 7.1.2 released (GitHub advisory date indicates fix was available earlier) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63205 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-63205?

Check whether you run Zammad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63205: Zammad authorization bypass via email signature attachments

CVE-2026-63205 · Severity: info · Published 2026-09-25

Zammad is a web-based helpdesk system that processes images referenced in email signatures. Channel administrators can exploit a flaw in signature creation to copy and download attachments they shouldn't have access to—such as files from tickets in groups they don't belong to. An attacker with channel admin permissions can read sensitive attachments by embedding references to them in a signature, bypassing normal access controls.

Technologies: Zammad. Vendors: Zammad.

Quick answers

Is CVE-2026-63205 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63205 being exploited in the wild.
How severe is CVE-2026-63205?: Informational severity, published 25 September 2026.
Which products and versions are affected?: Zammad prior to 7.1.2.
Is there a fix for CVE-2026-63205?: A patch was published on 2026-08-04: Version 7.1.2 released (GitHub advisory date indicates fix was available earlier) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63205 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-63205?: Check whether you run Zammad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

When Zammad creates or updates an email signature containing inline images (HTML img tags), it copies referenced attachments without verifying the user has permission to access the original. The copied attachment is owned by the signature object, so attachment access control checks are bypassed; permissions are evaluated against the signature (which the admin created) rather than the original object. An authenticated user with admin.channel_email, admin.channel_google, admin.channel_microsoft365, or admin.channel_microsoft_graph role can exploit this to read attachments from restricted tickets or knowledge-base articles.

Affected products

Zammad Zammad prior to 7.1.2

Timeline

2026-09-25: disclosed
2026-08-04: patched: Version 7.1.2 released (GitHub advisory date indicates fix was available earlier)

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.