# CVE-2025-64431: IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering

> Authenticated administrators can modify organization data across tenants due to missing authorization checks in the API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Nov 2025
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-cpf4-pmr4-w6cx, GO-2025-4099

## What is CVE-2025-64431?

CVE-2025-64431 is a high-severity missing authorization vulnerability in zitadel, published on 7 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-64431?

5 open source packages ship an affected version, including github.com/zitadel/zitadel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zitadel/zitadel` | Go | From 1.80.0-v2.20.0.20250414095945-f365cee73242 | 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 |
| `github.com/zitadel/zitadel` | Go | From 1.80.0-v2.20.0.20250414095945-f365cee73242 | 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 |
| `github.com/zitadel/zitadel` | Go | From 1.80.0-v2.20.0.20250414095945-f365cee73242 | 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 |
| `github.com/zitadel/zitadel` | Go | From 4.0.0-rc.1 | 4.6.3 |
| `github.com/zitadel/zitadel` | Go | From 4.0.0-rc.1 | 4.6.3 |

## How do I fix CVE-2025-64431?

Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 1.80.0-v2.20.0.20251105083648-8dcfff97ed52 or 4.6.3.

## Is CVE-2025-64431 being exploited?

There is no known exploitation of CVE-2025-64431 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64431 and fix it if it is affected.

What it is: CVE-2025-64431 is a high-severity missing authorization vulnerability in zitadel, published on 7 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64431 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zitadel/zitadel (Go): affected from 1.80.0-v2.20.0.20250414095945-f365cee73242; fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- github.com/zitadel/zitadel (Go): affected from 1.80.0-v2.20.0.20250414095945-f365cee73242; fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- github.com/zitadel/zitadel (Go): affected from 1.80.0-v2.20.0.20250414095945-f365cee73242; fixed in 1.80.0-v2.20.0.20251105083648-8dcfff97ed52
- github.com/zitadel/zitadel (Go): affected from 4.0.0-rc.1; fixed in 4.6.3
- github.com/zitadel/zitadel (Go): affected from 4.0.0-rc.1; fixed in 4.6.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64431/ (Markdown: https://insights.sbomify.com/CVE-2025-64431/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64431
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64431
- OSV: https://osv.dev/vulnerability/CVE-2025-64431

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64431/
Summaries are generated and may contain mistakes; the official description above is the record.