CVE-2025-64717: ZITADEL vulnerable to Account Takeover with deactivated Instance IdP

Published Nov 13, 2025
·
Updated

Summary

A vulnerability in ZITADEL's federation process allowed auto-linking users from external identity providers to existing users in ZITADEL even if the corresponding IdP was not active or if the organization did not allow federated authentication.

Impact

This vulnerability stems from the platform's failure to correctly check or enforce an organization's specific security settings during the authentication flow. An Organization Administrator can explicitly disable an IdP or disallow federation, but this setting was not being honored during the auto-linking process.

This allowed an unauthenticated attacker to initiate a login using an IdP that should have been disabled for that organization. The platform would incorrectly validate the login and, based on a matching criteria, link the attacker's external identity to an existing internal user account.

This may result in a full Account Takeover, bypassing the organization's mandated security controls. Note that accounts with MFA enabled can not be taken over by this attack. Also note that only IdPs create on an instance level would allow this to work. IdPs registered on another organization would always be denied in the (auto-)linking process.

Affected Versions

Systems running one of the following versions are affected: - v4.x: 4.0.0-rc.1 through 4.6.5 - v3.x: 3.0.0-rc.1 through 3.4.3 - v2.x: 2.50.0 through 2.71.18

Patches

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the organization's login policy before auto-linking an external user.

- v4.x: Upgrade to version 4.6.6 or later. - v3.x: Update to version 3.4.4 or later. - v2.x: Update to version 2.71.19 or later.

Workarounds

Upgrading to a patched version is the recommended solution.

Questions

If you have any questions or comments about this advisory, please email Zitadel at security@zitadel.com

Credits

Thanks to Jan Kühnlein - kultify for finding and reporting the vulnerability.

Other sources

ZITADEL is an open source identity management platform. Starting in version 2.50.0 and prior to versions 2.71.19, 3.4.4, and 4.6.6, a vulnerability in ZITADEL's federation process allowed auto-linking users from external identity providers to existing users in ZITADEL even if the corresponding IdP was not active or if the organization did not allow federated authentication. This vulnerability stems from the platform's failure to correctly check or enforce an organization's specific security settings during the authentication flow. An Organization Administrator can explicitly disable an IdP or disallow federation, but this setting was not being honored during the auto-linking process. This allowed an unauthenticated attacker to initiate a login using an IdP that should have been disabled for that organization. The platform would incorrectly validate the login and, based on a matching criteria, link the attacker's external identity to an existing internal user account. This may result in a full Account Takeover, bypassing the organization's mandated security controls. Note that accounts with MFA enabled can not be taken over by this attack. Also note that only IdPs create on an instance level would allow this to work. IdPs registered on another organization would always be denied in the (auto-)linking process. Versions 4.6.6, 3.4.4, and 2.71.19 resolve the issue by correctly validating the organization's login policy before auto-linking an external user. No known workarounds are available aside from upgrading.

— MITRE

Affected Software

8 affected componentsFixes available
ZITADEL ZITADEL>=2.50.0<2.71.19, <3.4.4, <4.6.6
go/github.com/zitadel/zitadel>=1.80.0-v2.20.0.20240403060621-5b3946b67ef6<1.80.0-v2.20.0.20251112124840-33c51deb2040
1.80.0-v2.20.0.20251112124840-33c51deb2040
go/github.com/zitadel/zitadel>=2.50.0<2.71.19
2.71.19
go/github.com/zitadel/zitadel>=3.0.0-rc.1<3.4.4
3.4.4
go/github.com/zitadel/zitadel>=4.0.0-rc.1<4.6.6
4.6.6
ZITADEL ZITADEL>=2.50.0<2.71.19
ZITADEL ZITADEL>=3.0.0<3.4.4
ZITADEL ZITADEL>=4.0.0<4.6.6

Event History

Nov 13, 2025
CVE Published
via MITRE·03:30 PM
Data Sourced
via MITRE·03:30 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
RemedyAffected Software
Nov 14, 2025
Advisory Published
via GitHub·09:11 PM
Data Sourced
via GitHub·09:11 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-64717?

CVE-2025-64717 is considered a high severity vulnerability due to its potential to allow unauthorized user auto-linking.

2

How do I fix CVE-2025-64717?

To fix CVE-2025-64717, upgrade ZITADEL to versions 2.71.19, 3.4.4, or 4.6.6 or later.

3

Who is affected by CVE-2025-64717?

CVE-2025-64717 affects ZITADEL versions starting from 2.50.0 and prior to 2.71.19, 3.4.4, and 4.6.6.

4

What does CVE-2025-64717 exploit?

CVE-2025-64717 exploits a vulnerability in ZITADEL's federation process.

5

What impact does CVE-2025-64717 have on user data?

CVE-2025-64717 can lead to security risks by allowing unauthorized users to be linked to existing ZITADEL users.

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