How severe is CVE-2025-64717?

No CVSS score has been assigned to CVE-2025-64717 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-64717?

CVE-2025-64717 affects the following packages: github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel (Go). Ecosystems affected: Go.

How do I fix CVE-2025-64717?

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.

How do I detect CVE-2025-64717 in my Go dependencies?

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.

How do I mitigate CVE-2025-64717 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-64717?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64717 can be triaged on real exposure rather than presence alone.

Is CVE-2025-64717 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-64717 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-64717?

CVE-2025-64717 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-64717?

CVE-2025-64717 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-64717 published, and has it been updated?

CVE-2025-64717 was published on November 13, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-64717 — zitadel

Fix: zitadel/zitadel@33c51de

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 asGHSA-j4g7-v4m4-77pxGO-2025-4124

Published

Nov 13, 2025

Updated

Aug 12, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 25, 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 ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 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 [email protected]

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`

Detection & mitigation playbook

Open-source dependency

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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64717 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-64717. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds CVE-2025-64717 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVE-2025-64717 — zitadel

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Impact

Affected Versions

Patches

Workarounds

Questions

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2025-64717 in your dependencies?