ZITADEL is vulnerable to Account Takeover with deactivated Instance IdP

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 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 · score source

EPSS

• CVE-2025-64717: 0.50% estimated exploitation activity in the next 30 days; percentile 42.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

14 Nov 2025, 21:11 UTC

Last modified by the source

14 Nov 2025, 21:11 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j4g7-v4m4-77px

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64717

Advisory: ZITADEL is vulnerable to Account Takeover with deactivated Instance IdP
IDs: CVE-2025-64717, GHSA-j4g7-v4m4-77px
Record: https://patchnext.com/advisories/cve-2025-64717 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 4.6.6, 3.4.4, 2.71.19, 1.80.0-v2.20.0.20251112124840-33c51deb2040. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected >= 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; fixed in 3.4.4, 1.80.0-v2.20.0.20251112124840-33c51deb2040, 4.6.6, 2.71.19

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j4g7-v4m4-77px (GitHub-reviewed advisory GHSA-j4g7-v4m4-77px lists affected ranges: Go github.com/zitadel/zitadel >=4.0.0-rc.1 =3.0.0-rc.1 =2.50.0 =1.80.0-v2.20.0.20240403060621-5b3946b67ef6 <1.80.0-v2.20.0.20251112124840-33c51deb2040)

Commands are suggestions: review each one before running it.