# CVE-2025-64717: zitadel — Fixed in 4.6.6 🐹 Go Not in CISA KEV # CVE-2025-64717 — zitadel [Fix: zitadel/zitadel@33c51de](https://github.com/zitadel/zitadel/commit/33c51deb20402dd5720e32cfb0c1d5fdc752f2e0) CVE-2025-64717 is a Improper Authentication vulnerability in github.com/zitadel/zitadel. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below. ZITADEL vulnerable to Account Takeover with deactivated Instance IdP Also known as[GHSA-j4g7-v4m4-77px](/vulnerability/GHSA-j4g7-v4m4-77px)GO-2025-4124 Published Nov 13, 2025 Updated Oct 28, 2026 Affected 4 pkgs Patched 4 / 4 Exploits None indexed Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64717. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.5%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk 0.00%0.40%0.80%1.20%0.7%0.5%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 4 pkgs affected 🐹`github.com/zitadel/zitadel`🐹`github.com/zitadel/zitadel`🐹`github.com/zitadel/zitadel`🐹`github.com/zitadel/zitadel` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems. ## Description #### 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](https://github.com/zitadel/zitadel/releases/tag/v4.6.6) or later. - v3.x: Update to version [3.4.4](https://github.com/zitadel/zitadel/releases/tag/v3.4.4) or later. - v2.x: Update to version [2.71.19](https://github.com/zitadel/zitadel/releases/tag/v2.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](mailto:security@zitadel.com) #### Credits Thanks to Jan Kühnlein - kultify for finding and reporting the vulnerability. ## Affected Packages 4 total 4 fixed Ecosystem Package Vulnerable range Fix 🐹Go `github.com/zitadel/zitadel` ≥ 4.0.0-rc.1&&< 4.6.6 4.6.6`go get github.com/zitadel/zitadel@v4.6.6` 🐹Go `github.com/zitadel/zitadel` ≥ 3.0.0-rc.1&&< 3.4.4 3.4.4`go get github.com/zitadel/zitadel@v3.4.4` 🐹Go `github.com/zitadel/zitadel` ≥ 2.50.0&&< 2.71.19 2.71.19`go get github.com/zitadel/zitadel@v2.71.19` 🐹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 get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251112124840-33c51deb2040` ## Affected Products 1 product · 3 configurations Application `zitadel`zitadel ≥ 4.0.0 && < 4.6.6 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update github.com/zitadel/zitadel to 4.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64717 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions \### 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 O3 Security · Impact-Aware SCA ### Is CVE-2025-64717 in your dependencies? Find it across Go, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)