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-84458 Overview
Zammad, an open source helpdesk and customer support platform, contains an authentication bypass vulnerability in its single sign-on (SSO) account linking logic. When the Automatic account link on initial logon setting is enabled, Zammad links an incoming third-party identity to an existing local account purely by matching the email address claimed by the identity provider. Zammad does not verify that the provider confirmed ownership of that email address.
An attacker who controls any identity at a configured provider can set that identity's email to a victim's address and authenticate as the victim. The flaw affects all account types, including agents and administrators. The issue is fixed in Zammad 7.1.2.
Critical Impact
Any attacker with an account in a configured identity provider, including any Azure AD tenant through Zammad's multi-tenant Microsoft 365 /common app registration, can take over arbitrary Zammad accounts including administrators.
Affected Products
- Zammad helpdesk versions prior to 7.1.2
- Deployments with Automatic account link on initial logon enabled
- Zammad instances using the multi-tenant Microsoft 365 /common app registration
Discovery Timeline
- 2026-09-25 - CVE-2026-84458 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-84458
Vulnerability Analysis
The vulnerability is an authentication bypass [CWE-287] in Zammad's SSO account linking workflow. When processing a successful third-party authentication, Zammad calls User.find_by(email: info['email'].downcase) to locate a matching local account and then logs the SSO identity in as that user. The code never asks the identity provider whether the email address was verified.
Attackers who register or modify any identity at a trusted provider can set an arbitrary email address on that identity, authenticate against Zammad, and inherit the matching local account's permissions. Because the lookup bypasses the local password check entirely, agent and administrator accounts are fully exposed. In multi-tenant Microsoft 365 setups, every Azure AD tenant worldwide is implicitly trusted by the /common endpoint, dramatically widening the attack surface.
Root Cause
The root cause is missing verification of the email_verified state communicated by the identity provider. Microsoft Entra ID exposes verification through the optional xms_edov claim in the ID token, but Zammad did not consult it. Any string the provider placed in the email field was accepted as authoritative identity.
Attack Vector
An attacker creates or controls an identity at a configured OAuth or OIDC provider, sets its email to a Zammad victim's address, and initiates login. Zammad matches the email to the victim's local account and establishes an authenticated session as that user. For Microsoft 365 multi-tenant deployments, no prior relationship with the Zammad organization is required.
# Patch excerpt: app/models/authorization/provider/microsoft_office365.rb
class Authorization::Provider::MicrosoftOffice365 < Authorization::Provider
private
def find_user
return if info['email'].nil?
return if !email_verified?
User.find_by(email: info['email'].downcase)
end
# In multi-tenant (/common) setups any Azure user worldwide could present an
# arbitrary email address. Microsoft signals whether the email is verified on
# the owning domain via the "xms_edov" claim in the ID token. The claim is
# extracted via OmniAuth::Strategies::MicrosoftOffice365Database#extra and
# stored under extra.id_token_claims.xms_edov.
Source: GitHub Commit 0dba387
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-84458
Indicators of Compromise
- Successful SSO logins where the incoming identity's uid or tenant ID differs from previously observed values for an existing user account.
- Microsoft 365 ID tokens arriving without the xms_edov claim, or with xms_edov=false, that still result in account linking.
- Authentication events for administrator or agent accounts originating from Azure AD tenants not associated with the organization.
Detection Strategies
- Audit Zammad authentication logs for first-time SSO logins against pre-existing local accounts, particularly privileged users.
- Correlate the OAuth provider uid and tenant identifier against a baseline of expected values for each user.
- Review Entra ID sign-in logs for successful token issuance to the Zammad application from unexpected tenants.
Monitoring Recommendations
- Enable detailed logging on the Zammad authentication provider stack and ingest it into a central SIEM.
- Alert on changes to the Automatic account link on initial logon setting and on new OAuth provider configurations.
- Monitor administrator-role sessions for unusual source IP addresses or geolocation changes immediately following SSO authentication.
How to Mitigate CVE-2026-84458
Immediate Actions Required
- Upgrade Zammad to version 7.1.2 or later without delay.
- Disable the Automatic account link on initial logon setting until upgrade is complete.
- Rotate credentials and review session activity for all agent and administrator accounts.
- For Microsoft 365 deployments, configure the email and xms_edov optional claims on the Entra ID app registration and enable require_verified_email_domain.
Patch Information
The fix is delivered in Zammad 7.1.2. The patch introduces an email_verified? check in Authorization::Provider subclasses and a dedicated find_user override in Authorization::Provider::MicrosoftOffice365 that honors the xms_edov ID token claim. See GitHub Security Advisory GHSA-86cc and the upstream commit 0dba387 for full details.
Workarounds
- Switch Microsoft 365 integration from the multi-tenant /common endpoint to a single-tenant app registration restricted to the organization's own tenant.
- Disable automatic account linking and require administrators to manually associate SSO identities with local accounts.
- Restrict SSO provider access through conditional access policies that limit sign-in to approved tenants and user groups.
# Zammad administrative console: disable automatic SSO account linking
rails r "Setting.set('auth_third_party_auto_link_at_inital_login', false)"
# Verify the setting after change
rails r "puts Setting.get('auth_third_party_auto_link_at_inital_login')"
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

