# CVE-2025-27507: IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations > Authenticated users can modify sensitive LDAP settings via IDOR in ZITADEL Admin API, requiring upgrade to patched versions. - **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Mar 2025 - **Updated:** 12 Mar 2025 - **Also known as:** GHSA-f3gh-529w-v32x, GO-2025-3499 ## What is CVE-2025-27507? CVE-2025-27507 is a critical missing authorization vulnerability in zitadel, published on 4 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. ZITADEL's Admin API contains Insecure Direct Object Reference (IDOR) vulnerabilities that allow authenticated users, without specific IAM roles, to modify sensitive settings. While several endpoints are affected, the most critical vulnerability lies in the ability to manipulate LDAP configurations. Customers who do not utilize LDAP for authentication are not at risk from the most severe aspects of this vulnerability. However, upgrading to the patched version to address all identified issues is strongly recommended. This vulnerability is fixed in 2.71.0, 2.70.1, ,2.69.4, 2.68.4, 2.67.8, 2.66.11, 2.65.6, 2.64.5, and 2.63.8. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2025-27507? 33 open source packages ship an affected version, including github.com/zitadel/zitadel and github.com/zitadel/zitadel/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/zitadel/zitadel` | Go | All versions | None | | `github.com/zitadel/zitadel` | Go | All versions | 2.63.8 | | `github.com/zitadel/zitadel` | Go | All versions | 2.63.8 | | `github.com/zitadel/zitadel` | Go | From 2.64.0 | 2.64.5 | | `github.com/zitadel/zitadel` | Go | From 2.64.0 | 2.64.5 | | `github.com/zitadel/zitadel` | Go | From 2.65.0 | 2.65.6 | | `github.com/zitadel/zitadel` | Go | From 2.65.0 | 2.65.6 | | `github.com/zitadel/zitadel` | Go | From 2.66.0 | 2.66.11 | | `github.com/zitadel/zitadel` | Go | From 2.66.0 | 2.66.11 | | `github.com/zitadel/zitadel` | Go | From 2.67.0 | 2.67.8 | | `github.com/zitadel/zitadel` | Go | From 2.67.0 | 2.67.8 | | `github.com/zitadel/zitadel` | Go | From 2.68.0 | 2.68.4 | | `github.com/zitadel/zitadel` | Go | From 2.68.0 | 2.68.4 | | `github.com/zitadel/zitadel` | Go | From 2.69.0 | 2.69.4 | | `github.com/zitadel/zitadel` | Go | From 2.69.0 | 2.69.4 | | `github.com/zitadel/zitadel` | Go | From 2.70.0 | 2.70.1 | | `github.com/zitadel/zitadel` | Go | From 2.70.0 | 2.70.1 | | `github.com/zitadel/zitadel/v2` | Go | All versions | 2.63.8 | | `github.com/zitadel/zitadel/v2` | Go | All versions | 2.63.8 | | `github.com/zitadel/zitadel/v2` | Go | From 2.64.0 | 2.64.5 | | `github.com/zitadel/zitadel/v2` | Go | From 2.64.0 | 2.64.5 | | `github.com/zitadel/zitadel/v2` | Go | From 2.65.0 | 2.65.6 | | `github.com/zitadel/zitadel/v2` | Go | From 2.65.0 | 2.65.6 | | `github.com/zitadel/zitadel/v2` | Go | From 2.66.0 | 2.66.11 | | `github.com/zitadel/zitadel/v2` | Go | From 2.66.0 | 2.66.11 | | `github.com/zitadel/zitadel/v2` | Go | From 2.67.0 | 2.67.8 | | `github.com/zitadel/zitadel/v2` | Go | From 2.67.0 | 2.67.8 | | `github.com/zitadel/zitadel/v2` | Go | From 2.68.0 | 2.68.4 | | `github.com/zitadel/zitadel/v2` | Go | From 2.68.0 | 2.68.4 | | `github.com/zitadel/zitadel/v2` | Go | From 2.69.0 | 2.69.4 | | `github.com/zitadel/zitadel/v2` | Go | From 2.69.0 | 2.69.4 | | `github.com/zitadel/zitadel/v2` | Go | From 2.70.0 | 2.70.1 | | `github.com/zitadel/zitadel/v2` | Go | From 2.70.0 | 2.70.1 | Products: Zitadel Zitadel. ## How do I fix CVE-2025-27507? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 2.63.8, 2.64.5, 2.65.6 or 2.66.11. ## Is CVE-2025-27507 being exploited? There is no known exploitation of CVE-2025-27507 in the wild and no public exploit code. ## Other vulnerabilities in zitadel - [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) - [CVE-2024-29891](https://insights.sbomify.com/CVE-2024-29891/): ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-27507 and fix it if it is affected. What it is: CVE-2025-27507 is a critical missing authorization vulnerability in zitadel, published on 4 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-27507 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel (Go): affected all versions; no fix listed - github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.63.8 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.63.8 - github.com/zitadel/zitadel (Go): affected from 2.64.0; fixed in 2.64.5 - github.com/zitadel/zitadel (Go): affected from 2.64.0; fixed in 2.64.5 - github.com/zitadel/zitadel (Go): affected from 2.65.0; fixed in 2.65.6 - github.com/zitadel/zitadel (Go): affected from 2.65.0; fixed in 2.65.6 - github.com/zitadel/zitadel (Go): affected from 2.66.0; fixed in 2.66.11 - github.com/zitadel/zitadel (Go): affected from 2.66.0; fixed in 2.66.11 - github.com/zitadel/zitadel (Go): affected from 2.67.0; fixed in 2.67.8 - github.com/zitadel/zitadel (Go): affected from 2.67.0; fixed in 2.67.8 - github.com/zitadel/zitadel (Go): affected from 2.68.0; fixed in 2.68.4 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-27507/ (Markdown: https://insights.sbomify.com/CVE-2025-27507/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27507 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27507 - OSV: https://osv.dev/vulnerability/CVE-2025-27507 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-27507/ Summaries are generated and may contain mistakes; the official description above is the record.