# CVE-2026-63207: Zammad: Sensitive Information Exposure in Integration Administration API

> An authenticated administrator can retrieve stored integration credentials in cleartext via the API due to inconsistent masking of sensitive fields.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-48h2-wv8r-fgp9

## What is CVE-2026-63207?

CVE-2026-63207 is a medium-severity vulnerability in zammad, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Zammad is a web based open source helpdesk/customer support system. In 7.0.3 and 7.1.1, an authenticated administrator can obtain stored integration credentials in cleartext through the integration administration API. Certain responses do not consistently mask sensitive fields, so configured secrets can be returned in plain text instead of the expected masked placeholder. Both the LDAP and Exchange integrations are affected. This issue is fixed in version 7.1.2.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-63207?


## How do I fix CVE-2026-63207?

No fix has been published for CVE-2026-63207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63207 being exploited?

There is no known exploitation of CVE-2026-63207 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63207 and fix it if it is affected.

What it is: CVE-2026-63207 is a medium-severity vulnerability in zammad, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63207 in the wild and no public exploit code.

Affected product: zammad. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63207/ (Markdown: https://insights.sbomify.com/CVE-2026-63207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63207
- OSV: https://osv.dev/vulnerability/CVE-2026-63207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63207/
Summaries are generated and may contain mistakes; the official description above is the record.