CVE-2025-64431: IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering
Summary 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.
Published Nov 5, 2025 · Updated Nov 7, 2025
Affected packages
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 4.0.0-rc.1, < 4.6.2
- Fixed in
- 4.6.3
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 1.80.0-v2.20.0.20250414095945-f365cee73242, < 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- Fixed in
- 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- Check
go list -m github.com/zitadel/zitadel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Impact
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.
Affected Versions
Systems running one of the following versions are affected:
- v4.x:
4.0.0-rc.1through4.6.2
Patches
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.
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]](mailto:[email protected])
Credited to livio-a, stebenz.
References
- https://github.com/zitadel/zitadel/security/advisories/GHSA-cpf4-pmr4-w6cx
- https://github.com/zitadel/zitadel/commit/8dcfff97ed52a8b9fc77ecb1f972744f42cff3ed
- https://github.com/zitadel/zitadel/releases/tag/v4.6.3
- https://nvd.nist.gov/vuln/detail/CVE-2025-64431
- https://github.com/advisories/GHSA-cpf4-pmr4-w6cx
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-85056
ZITADEL: MFA bypass via session reuse in Login V2
high8.2Sep 24, 2026CVE-2026-85057
ZITADEL: Actions V1 sandbox escape: host file read via require()
high8.7Sep 24, 2026CVE-2026-56668
ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange
high8.1Sep 14, 2026CVE-2026-76081
ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions
medium5.5Sep 14, 2026CVE-2026-56665
ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
medium4.2Sep 11, 2026CVE-2026-56666
ZITADEL: Auto-linking by email: IdP-side email verification is not checked
medium4.8Sep 11, 2026
