CVE-2026-56666: ZITADEL: Auto-linking by email: IdP-side email verification is not checked

Published Jul 10, 2026
·
Updated

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 3.x: Upgrade to $\ge$ 4.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 AUTOLINKINGOPTIONUNSPECIFIED 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 security@zitadel.com

Credits

Thanks to Android-Login-Analysis and Alejandro Yadlin for reporting this vulnerability.

Other sources

ZITADEL is an open source identity management platform. Prior to 4.15.3, ZITADEL's external identity provider handler checks that the local user's email is verified but does not verify that the external IdP confirmed ownership of the same email before auto-linking by email, allowing a permissive provider account with a victim email address to be linked to the victim's local account. This issue is fixed in version 4.15.3.

— MITRE

Affected Software

2 affected componentsFixes available
ZITADEL ZITADEL<4.15.3
go/github.com/zitadel/zitadel<4.15.3
4.15.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/zitadel/zitadel to a version that resolves this vulnerability.

    Fixed in 4.15.3
  2. Upgrade

    Upgrade zitadel to a version that resolves this vulnerability.

    Fixed in 4.15.3
  3. Configuration

    Disable auto-linking by email entirely by setting the AUTO_LINKING_OPTION_UNSPECIFIED option on corresponding identity providers.

    ZITADEL external identity providers AUTO_LINKING_OPTION_UNSPECIFIED = AUTO_LINKING_OPTION_UNSPECIFIED
  4. Compensating control

    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.

Event History

Jul 10, 2026
CVE Published
via MITRE·05:37 PM
Data Sourced
via MITRE·05:37 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeakness
Sep 11, 2026
Advisory Published
via GitHub·10:13 PM
Data Sourced
via GitHub·10:13 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-56666?

The severity of CVE-2026-56666 is rated as medium with a score of 4.8.

2

How do I fix CVE-2026-56666?

To fix CVE-2026-56666, upgrade ZITADEL to version 4.15.3 or later.

3

What vulnerability does CVE-2026-56666 address?

CVE-2026-56666 addresses the lack of external identity provider email verification during auto-linking.

4

Is my ZITADEL instance vulnerable to CVE-2026-56666?

If your ZITADEL instance is running a version prior to 4.15.3, it is vulnerable to CVE-2026-56666.

5

What impact does CVE-2026-56666 have on identity management?

CVE-2026-56666 may allow unauthorized auto-linking of user accounts if the external identity provider's email ownership is not verified.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203