CVE-2025-64717: GO-2025-4124 - ZITADEL is vulnerable to Account Takeover with deactivated Instance IdP in github.com/zitadel/zitadel

CVE-2025-64717 · Severity: critical · CVSS 9.8 · Published 2025-11-13

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.

Technologies: github.com/zitadel/zitadel (Go), ZITADEL. Vendors: Go, ZITADEL.

Quick answers

Is CVE-2025-64717 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-64717 being exploited in the wild.
How severe is CVE-2025-64717?
Critical severity, with a CVSS score of 9.8, published 13 November 2025.
Which products and versions are affected?
github.com/zitadel/zitadel (Go) SEMVER:introduced=1.80.0-v2.20.0.20240403060621-5b3946b67ef6,fixed=1.80.0-v2.20.0.20251112124840-33c51deb2040, SEMVER:introduced=4.0.0-rc.1,fixed=4.6.6.
Is there a fix for CVE-2025-64717?
Yes. github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20251112124840-33c51deb2040, 4.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-64717?
Check whether you run github.com/zitadel/zitadel (Go) or ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20251112124840-33c51deb2040, 4.6.6 or later
    go get github.com/zitadel/zitadel@v4.6.6

Affected products

  • github.com/zitadel/zitadel (Go) SEMVER:introduced=1.80.0-v2.20.0.20240403060621-5b3946b67ef6,fixed=1.80.0-v2.20.0.20251112124840-33c51deb2040, SEMVER:introduced=4.0.0-rc.1,fixed=4.6.6
  • ZITADEL

Identifiers

  • CVE-2025-64717
  • GHSA-j4g7-v4m4-77px
  • GO-2025-4124

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.