CVE-2026-63207: Zammad sensitive information exposure in integration API

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

Zammad is an open source helpdesk and customer support system that manages support tickets and integrations with external services like LDAP and email systems. An authenticated administrator can retrieve stored integration credentials in plain text through the API instead of masked values, exposing passwords and secrets used to connect to critical backend systems. This could allow an administrator to compromise integrated email systems, directory services, and other connected infrastructure.

Technologies: Zammad. Vendors: Zammad.

Quick answers

Is CVE-2026-63207 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-63207 being exploited in the wild.
How severe is CVE-2026-63207?
Informational severity, published 25 September 2026.
Which products and versions are affected?
Zammad 7.0.3, 7.1.1.
Is there a fix for CVE-2026-63207?
A patch was published on 2026-08-04: Fixed in version 7.1.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63207 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-63207?
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

The integration administration API fails to consistently mask sensitive credential fields in responses for LDAP and Exchange integrations, returning plaintext secrets instead of masked placeholders. An authenticated administrator with access to the integration API can extract stored credentials. This requires administrative privileges and network access to the Zammad API; the vulnerability is fixed in version 7.1.2.

Affected products

  • Zammad Zammad 7.0.3, 7.1.1

Timeline

  • 2026-09-25: disclosed
  • 2026-08-04: patched: Fixed in version 7.1.2

References

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