Summary
CVE-2026-84458 is a critical authentication bypass vulnerability in Zammad, an open-source web-based helpdesk and customer support system. The flaw resides in Zammad’s "Automatic account link on initial logon" SSO feature, which links an incoming third-party identity to an existing local account by matching email addresses without verifying that the identity provider actually confirmed ownership of that email. The vulnerability carries a CVSS score of 9.1 (Critical) and allows a remote, unauthenticated attacker to take over any account, including administrators.
Technical details
- Root cause: when automatic account linking is enabled, Zammad binds an SSO identity to a local account solely on the basis of a matching email address, without confirming the identity provider verified that address.
- For Microsoft 365 logins, Zammad relies on the
xms_edovID token claim to determine whether an email has been verified; if the claim is absent, Zammad is expected to treat the email as unverified, but the flawed logic does not correctly enforce this. - Trigger conditions: the "Automatic account link on initial logon" setting must be enabled. Exposure is heightened by Zammad’s default use of a multi-tenant Microsoft 365 app registration (
/common), which allows an attacker to authenticate from any Azure AD tenant they control. - Attack vector: an attacker registers or controls an identity at a configured SSO provider, sets that identity’s email address to match a target victim’s email, and authenticates through SSO to Zammad.
- Impact: the attacker is logged in as the victim, bypassing the victim’s local password entirely. This can affect any account, including agents and administrators, resulting in full account takeover and access to sensitive helpdesk data.
Affected software
- Zammad versions <= 7.1.1
- Fixed in Zammad 7.1.2
Severity
- CVSS v4.0 Base Score: 9.1 (Critical)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: upgrade Zammad to version 7.1.2 or later.
- If upgrading is not immediately possible: disable the "Automatic account link on initial logon" setting to prevent SSO identities from being auto-linked to existing local accounts based on unverified email matches.
- Review SSO/Microsoft 365 login configuration and audit recent SSO logins for anomalies, particularly for administrator and agent accounts.

