Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-63207 Overview
Zammad is a web-based open source helpdesk and customer support system used by organizations to manage support operations. CVE-2026-63207 is an information disclosure vulnerability affecting Zammad versions 7.0.3 and 7.1.1. An authenticated administrator can retrieve stored integration credentials in cleartext through the integration administration API. Certain API responses fail to consistently mask sensitive fields, returning configured secrets in plain text instead of the expected masked placeholder. Both the Lightweight Directory Access Protocol (LDAP) and Microsoft Exchange integrations are affected. The issue is tracked as [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor].
Critical Impact
Authenticated administrators can retrieve LDAP and Exchange integration credentials in cleartext, enabling lateral movement into directory services and mail infrastructure if administrator accounts are compromised.
Affected Products
- Zammad version 7.0.3
- Zammad version 7.1.1
- Zammad LDAP and Exchange integration modules
Discovery Timeline
- 2026-09-25 - CVE-2026-63207 published to the National Vulnerability Database
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-63207
Vulnerability Analysis
The vulnerability resides in Zammad's integration administration API, which handles configuration data for external systems such as LDAP directories and Microsoft Exchange servers. When administrators configure these integrations, Zammad stores credentials including passwords and OAuth access tokens. The expected behavior is to return masked placeholder values in API responses to prevent credential exposure in the browser or API client.
The affected code paths in app/controllers/integration/exchange_controller.rb and the shared Integration::ImportJobBase concern did not define a complete list of sensitive fields that must be masked during dry-run operations. As a result, API responses returned raw values for fields such as payload.ews_config.password and payload.ews_config.access_token. The same inconsistency affected the LDAP integration flow.
Exploitation requires high privileges, as only authenticated administrators can reach the integration API. However, exposure of these credentials enables an attacker who compromises an administrator account to pivot into connected directory and mail systems.
Root Cause
The root cause is incomplete sensitive-field masking logic in the integration controllers. The upstream Integration::ImportJobBase module did not declare an IMPORT_JOB_SENSITIVE_FIELDS constant, and individual integration controllers did not override it with the full list of secret-bearing field paths. Dry-run and index responses therefore serialized credential fields verbatim.
Attack Vector
An authenticated administrator sends a request to the integration administration API endpoints that return LDAP or Exchange configuration data. The response body contains the stored credentials in cleartext rather than a masked placeholder, exposing them to anyone with access to the HTTP response, browser developer tools, or proxy logs.
# Security patch in app/controllers/integration/exchange_controller.rb
# Declares the sensitive fields that must be masked in dry-run responses
prepend_before_action :authenticate_and_authorize!
IMPORT_JOB_SENSITIVE_FIELDS = %w[payload.ews_config.password payload.ews_config.access_token].freeze
def index
assets = {}
external_credential_ids = []
Source: Zammad commit fab2e2e9
The shared concern also adds the baseline constant for all integration controllers to override:
# Security patch in app/controllers/concerns/integration/import_job_base.rb
module Integration::ImportJobBase
extend ActiveSupport::Concern
IMPORT_JOB_SENSITIVE_FIELDS = [].freeze
def job_try_index
job_index(
dry_run: true,
Source: Zammad commit fab2e2e9
Detection Methods for CVE-2026-63207
Indicators of Compromise
- Administrator-initiated requests to Zammad integration endpoints such as /api/v1/integration/exchange or /api/v1/integration/ldap returning payloads containing non-masked password or access_token fields.
- Unexpected authentication activity in LDAP or Exchange logs originating from service accounts configured in Zammad integrations.
- Access to integration configuration endpoints from administrator sessions outside normal change-management windows.
Detection Strategies
- Inspect Zammad application and reverse-proxy logs for GET or POST calls against integration administration endpoints, correlating with administrator user IDs.
- Review web server response captures for the presence of cleartext credential fields in JSON responses returned by integration APIs.
- Audit the Zammad database for unexpected administrator role assignments that could abuse the integration API.
Monitoring Recommendations
- Enable verbose audit logging for all Zammad administrator actions, including integration read operations.
- Forward Zammad access logs to a central SIEM and alert on access to /api/v1/integration/* paths outside approved maintenance windows.
- Monitor LDAP bind events and Exchange Web Services (EWS) authentication for the service accounts configured in Zammad integrations.
How to Mitigate CVE-2026-63207
Immediate Actions Required
- Upgrade Zammad to version 7.1.2 or later, which includes the masking fix in commit fab2e2e9.
- Rotate all credentials and OAuth access tokens configured for LDAP and Exchange integrations in affected Zammad instances.
- Review Zammad administrator account inventory and remove unused or stale administrator privileges.
- Audit historical API logs for prior access to integration endpoints and treat any exposed credentials as compromised.
Patch Information
The vulnerability is fixed in Zammad version 7.1.2. The fix adds the IMPORT_JOB_SENSITIVE_FIELDS constant to the Integration::ImportJobBase concern and defines the specific sensitive field paths in integration controllers, ensuring that dry-run and index responses mask credential values. See the GitHub Security Advisory GHSA-48h2-wv8r-fgp9 for the full advisory.
Workarounds
- Restrict Zammad administrator role assignment to the minimum necessary personnel until upgrading to 7.1.2.
- Place Zammad administrative endpoints behind an authenticated reverse proxy with IP allow-listing.
- Use dedicated low-privilege service accounts for LDAP and Exchange integrations so that any exposure limits downstream blast radius.
# Verify your Zammad version and upgrade using the official package manager
zammad run rails r 'puts Version.get'
# Debian / Ubuntu example
sudo apt update && sudo apt install --only-upgrade zammad
# After upgrade, confirm the version is 7.1.2 or later
zammad run rails r 'puts Version.get'
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

