Read the docs
TI-2025-39844 Aliases CVE-2025-64431GHSA-cpf4-pmr4-w6cx

IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering

Priority LOW 39CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-639.

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00303 23rd percentileScored 2026-11-07
Fix Fixed zitadel (zitadel): 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52github.com/zitadel/zitadel (Go): 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
zitadelzitadel4.0.0-rc.1 to before 4.6.3; 1.80.0-v2.20.0.20250414095945-f365cee73242 to before 1.80.0-v2.20.0.20251105083648-8dcfff97ed524.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52Patch availableCNA
—github.com/zitadel/zitadel (Go)4.0.0-rc.1 to before 4.6.34.6.3Patch availableGHSA-cpf4-pmr4-w6cx
—github.com/zitadel/zitadel (Go)1.80.0-v2.20.0.20250414095945-f365cee73242 to before 1.80.0-v2.20.0.20251105083648-8dcfff97ed521.80.0-v2.20.0.20251105083648-8dcfff97ed52Patch availableGHSA-cpf4-pmr4-w6cx
  • zitadel Vendorzitadel Affected 4.0.0-rc.1 to before 4.6.3; 1.80.0-v2.20.0.20250414095945-f365cee73242 to before 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 Fixed in 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 Patch available CNA
  • github.com/zitadel/zitadel (Go) Vendor— Affected 4.0.0-rc.1 to before 4.6.3 Fixed in 4.6.3 Patch available GHSA-cpf4-pmr4-w6cx
  • github.com/zitadel/zitadel (Go) Vendor— Affected 1.80.0-v2.20.0.20250414095945-f365cee73242 to before 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 Fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 Patch available GHSA-cpf4-pmr4-w6cx

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:*——zitadel
  • cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* Versions — — ·zitadel

Remediation

  • Fix · CNA zitadel (zitadel) Fixed in 4.6.3, 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
  • Fix · GHSA-cpf4-pmr4-w6cx github.com/zitadel/zitadel (Go) Fixed in 4.6.3 Advisory →
  • Fix · GHSA-cpf4-pmr4-w6cx github.com/zitadel/zitadel (Go) Fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-64431
  2. 2026-10-03 Alias added: GHSA-cpf4-pmr4-w6cx

References

Advisory 1

Other 4

  • TI-2024-26607 ZITADEL Vulnerable to Session Information Leakage CVSS 3.1MEDIUM 6.5
  • TI-2026-67551 ZITADEL before 4.16.2 Account Pre-Hijacking via Forged External IdP Callback CVSS 4.0CRITICAL 9.3
  • TI-2026-67543 ZITADEL before 4.17.3 Account Takeover via External IdP Linking CVSS 4.0CRITICAL 9.3
  • TI-2025-41253 ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login CVSS 3.1CRITICAL 9.3
  • TI-2025-39554 Zitadel Bypass Second Authentication Factor CVSS 4.0HIGH 8.7
  • TI-2026-82647 ZITADEL Login V2 flaw lets attackers approve device authorizations CVSS 4.0HIGH 8.6
See all 77 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences