CVE-2025-64717 json
ZITADEL vulnerable to Account Takeover with deactivated Instance IdP
published 2025-11-13 11 mo ago modified 2026-10-19 21 d ago also EUVD-2025-175316 , GHSA-j4g7-v4m4-77px , GO-2025-4124
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/zitadel/zitadel 1.80.0-v2.20.0.20251112124840-33c51deb2040, 2.71.19, 3.4.4, 4.6.6
- zitadel zitadel 2.71.19, 3.4.4, 4.6.6
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11 mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.4 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 7.4 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zitadel/zitadel | >=4.0.0-rc.1, <4.6.6 >=3.0.0-rc.1, <3.4.4 >=2.50.0, <2.71.19 >=1.80.0-v2.20.0.20240403060621-5b3946b67ef6, <1.80.0-v2.20.0.20251112124840-33c51deb2040 |
4.6.6 3.4.4 2.71.19 1.80.0-v2.20.0.20251112124840-33c51deb2040 |
Affected products
- zitadel zitadel
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/zitadel/zitadel/security/advisories/GHSA-j4g7-v4m4-77px
web, patch, vendor-advisory, advisory
-
github.com
/zitadel/zitadel/commit/33c51deb20402dd5720e32cfb0c1d5fdc752f2e0
web, patch
-
github.com
/zitadel/zitadel/releases/tag/v2.71.19
web, release-notes
-
github.com
/zitadel/zitadel/releases/tag/v3.4.4
web, release-notes
-
github.com
/zitadel/zitadel/releases/tag/v4.6.6
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2025-64717
advisory
-
github.com
/zitadel/zitadel
package
Sources
- CVE List CVE-2025-64717
- GitHub Advisory GHSA-j4g7-v4m4-77px
- NVD CVE-2025-64717
- OSV GO-2025-4124
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.