CVE-2025-64431

ZITADEL's Organization V2Beta API contains Insecure Direct Object Reference (IDOR) vulnerabilities that allow authenticated users with specific administrator roles within one organization to access and modify data belonging to other organizations.

Affected Versions

Systems running one of the following versions are affected:

• v4.x: 4.0.0-rc.1 through 4.6.2

Workarounds

Upgrading to a patched version is the recommended solution.

If an immediate upgrade is not possible, mitigation can be achieved by disabling the affected Organization V2Beta API endpoints (e.g., /v2beta/organizations/...) at a reverse proxy or Web Application Firewall (WAF) level.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

ZITADEL's Organization V2Beta API, intended for managing ZITADEL organizations, contains multiple endpoints that fail to properly authorize authenticated users. An attacker with an administrator role for a specific organization could exploit this to bypass access controls and perform unauthorized actions on other organizations within the same ZITADEL instance.

This could allow an attacker to:

• Read organization data, including the name, domains and metadata.
• Manipulate (modify) the corresponding organization data.
• Delete the corresponding data, up to and including the entire organization.

Note that this vulnerability is limited to organization-level data (name, domains, metadata). No other related data (such as users, projects, applications, etc.) is affected.

Kodem intelligence

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the caller's permission against the target organization.

• v4.x: Upgrade to version 4.6.3 or later.

1. What is CVE-2025-64431? CVE-2025-64431 is a high-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 4.0.0-rc.1, < 4.6.2. It is fixed in 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52.
2. Which versions of github.com/zitadel/zitadel are affected by CVE-2025-64431? github.com/zitadel/zitadel (go) versions >= 4.0.0-rc.1, < 4.6.2 is affected.
3. Is there a fix for CVE-2025-64431? Yes. CVE-2025-64431 is fixed in 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52. Upgrade to this version or later.
4. Is CVE-2025-64431 exploitable, and should I be worried? Whether CVE-2025-64431 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-64431 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-64431?
   • Upgrade github.com/zitadel/zitadel to 4.6.3 or later
   • Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 or later