ZITADEL: Auto-linking by email: IdP-side email verification is not checked (CVE-2026-56666)
### Summary A flaw in the external identity provider handler allows unauthorized account linking to occur under specific administrative configurations. When auto-linking by email is enabled, ZITADEL checks that the local user's email is verified, but does not explicitly cross-check whether the incoming external identity provider (IdP) also verified that email address upstream. ### Impact When a user logs in via an external identity provider, the system can automatically link them to an existing local account if their email addresses match. However, because the system fails to check if the external provider actually verified ownership of that email, a security risk is introduced if a loose or public provider is connected. If an administrator enables email auto-linking for an external identity provider that allows anyone to sign up with an unverified email address, an attacker can exploit this behavior. By registering an account on that permissive provider using a victim's email address and logging in, the system will automatically link the attacker's federated identity to the victim's legitimate local account. This allows the attacker to log into the victim's account without requiring any interaction or confirmation from the victim. This issue represents a configuration-dependent anomaly rather than an unconditioned attack vector. Because the scenario relies entirely on an explicit administrative choice to trust a permissive external directory and link accounts automatically based purely on email strings, the practical operational risk is classified as **Medium**. ### Affected Versions Systems running one of the following versions are affected: * **4.x:** `4.0.0` through `4.15.2` (including RC versions) * **3.x:** `3.0.0` through `3.4.12` (including RC versions) ### Patches The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring that the external identity provider's email verification status is explicitly validated before allowing any automatic linking logic to proceed. * **4.x**: Upgrade to $\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3) * **3.x**: Upgrade to $\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3) ### Workarounds If an immediate upgrade is not possible, implement one of the following mitigations: * Disable auto-linking by email entirely by setting the option to `AUTO_LINKING_OPTION_UNSPECIFIED` on corresponding identity providers. * Audit external IdP configurations and restrict email auto-linking strictly to trusted enterprise identity directories (e.g., corporate Okta or Azure AD) where email verification is strictly enforced and managed by corporate policy. ### Questions If you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected]) ### Credits Thanks to [Android-Login-Analysis](https://github.com/Android-Login-Analysis) and [Alejandro Yadlin](https://github.com/ayadlin) for reporting this vulnerability.
AI Analysis
Technical Summary
The vulnerability in ZITADEL (CVE-2026-56666) arises from insufficient verification of email ownership from external identity providers during automatic account linking by email. While the local user's email verification is checked, the system does not confirm that the external IdP has verified the email address. If an administrator enables auto-linking with an external IdP that allows unverified email signups, an attacker can register using a victim's email and gain unauthorized access by linking to the victim's local account. This flaw is configuration-dependent and affects ZITADEL versions 3.0.0 through 3.4.12 and 4.0.0 through 4.15.2. The issue is fixed in version 4.15.3 and later by requiring explicit validation of the external IdP's email verification status before linking.
Potential Impact
The vulnerability allows an attacker to gain unauthorized access to a victim's local account by exploiting the automatic email-based account linking feature when used with an external identity provider that does not enforce email verification. This can lead to account compromise without victim interaction. However, the risk is medium and depends on the administrator enabling auto-linking with a permissive external IdP.
Mitigation Recommendations
A patch is available in ZITADEL version 4.15.3 and later that enforces verification of the external identity provider's email verification status before auto-linking accounts. Administrators should upgrade to these versions to remediate the vulnerability. If immediate upgrade is not possible, disable auto-linking by email on affected identity providers or restrict auto-linking to trusted enterprise identity providers that enforce strict email verification policies.
ZITADEL: Auto-linking by email: IdP-side email verification is not checked (CVE-2026-56666)
Description
### Summary A flaw in the external identity provider handler allows unauthorized account linking to occur under specific administrative configurations. When auto-linking by email is enabled, ZITADEL checks that the local user's email is verified, but does not explicitly cross-check whether the incoming external identity provider (IdP) also verified that email address upstream. ### Impact When a user logs in via an external identity provider, the system can automatically link them to an existing local account if their email addresses match. However, because the system fails to check if the external provider actually verified ownership of that email, a security risk is introduced if a loose or public provider is connected. If an administrator enables email auto-linking for an external identity provider that allows anyone to sign up with an unverified email address, an attacker can exploit this behavior. By registering an account on that permissive provider using a victim's email address and logging in, the system will automatically link the attacker's federated identity to the victim's legitimate local account. This allows the attacker to log into the victim's account without requiring any interaction or confirmation from the victim. This issue represents a configuration-dependent anomaly rather than an unconditioned attack vector. Because the scenario relies entirely on an explicit administrative choice to trust a permissive external directory and link accounts automatically based purely on email strings, the practical operational risk is classified as **Medium**. ### Affected Versions Systems running one of the following versions are affected: * **4.x:** `4.0.0` through `4.15.2` (including RC versions) * **3.x:** `3.0.0` through `3.4.12` (including RC versions) ### Patches The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring that the external identity provider's email verification status is explicitly validated before allowing any automatic linking logic to proceed. * **4.x**: Upgrade to $\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3) * **3.x**: Upgrade to $\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3) ### Workarounds If an immediate upgrade is not possible, implement one of the following mitigations: * Disable auto-linking by email entirely by setting the option to `AUTO_LINKING_OPTION_UNSPECIFIED` on corresponding identity providers. * Audit external IdP configurations and restrict email auto-linking strictly to trusted enterprise identity directories (e.g., corporate Okta or Azure AD) where email verification is strictly enforced and managed by corporate policy. ### Questions If you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected]) ### Credits Thanks to [Android-Login-Analysis](https://github.com/Android-Login-Analysis) and [Alejandro Yadlin](https://github.com/ayadlin) for reporting this vulnerability.
CVSS v3.1
Score 4.8medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in ZITADEL (CVE-2026-56666) arises from insufficient verification of email ownership from external identity providers during automatic account linking by email. While the local user's email verification is checked, the system does not confirm that the external IdP has verified the email address. If an administrator enables auto-linking with an external IdP that allows unverified email signups, an attacker can register using a victim's email and gain unauthorized access by linking to the victim's local account. This flaw is configuration-dependent and affects ZITADEL versions 3.0.0 through 3.4.12 and 4.0.0 through 4.15.2. The issue is fixed in version 4.15.3 and later by requiring explicit validation of the external IdP's email verification status before linking.
Potential Impact
The vulnerability allows an attacker to gain unauthorized access to a victim's local account by exploiting the automatic email-based account linking feature when used with an external identity provider that does not enforce email verification. This can lead to account compromise without victim interaction. However, the risk is medium and depends on the administrator enabling auto-linking with a permissive external IdP.
Mitigation Recommendations
A patch is available in ZITADEL version 4.15.3 and later that enforces verification of the external identity provider's email verification status before auto-linking accounts. Administrators should upgrade to these versions to remediate the vulnerability. If immediate upgrade is not possible, disable auto-linking by email on affected identity providers or restrict auto-linking to trusted enterprise identity providers that enforce strict email verification policies.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-992q-9gwp-7r79
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-56666"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6aa49fee55bf5e2cf5a860ab
Added to database: 09/12/2026, 00:42:22 UTC
Last enriched: 09/12/2026, 00:44:57 UTC
Last updated: 09/12/2026, 00:53:57 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.