IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Zitadel is an open source identity management platform. Versions 4.0.0-rc.1 through 4.6.2 are vulnerable to secure Direct Object Reference (IDOR) attacks through its V2Beta API, allowing authenticated users with specific administrator roles within one organization to access and modify data belonging to other organizations. 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. This issue is fixed in version 4.6.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- zitadel zitadel
From 4.0.0-rc.1 · fixed in 4.6.3; From 1.80.0-v2.20.0.20250414095945-f365cee73242 · fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- github.com/zitadel/zitadelGo
From 4.0.0-rc.1 · fixed in 4.6.3
- github.com/zitadel/zitadelGo
From 1.80.0-v2.20.0.20250414095945-f365cee73242 · fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52