CVE-2025-27507

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, we still strongly recommend upgrading to the patched version to address all identified issues.

Description

ZITADEL's Admin API, intended for managing ZITADEL instances, contains 12 HTTP endpoints that are unexpectedly accessible to authenticated ZITADEL users who are not ZITADEL managers. The most critical vulnerable endpoints relate to LDAP configuration:

• /idps/ldap
• /idps/ldap/{id}

By accessing these endpoints, unauthorized users could:

• Modify ZITADEL's instance LDAP settings, redirecting all LDAP login attempts to a malicious server, effectively taking over user accounts.
• Expose the original LDAP server's password, potentially compromising all user accounts.

Additional Vulnerable Endpoints

The following endpoints are also affected by IDOR vulnerabilities, potentially allowing unauthorized modification of instance settings such as languages, labels, and templates:

• /idps/templates/_search
• /idps/templates/{id}
• /policies/label/_activate
• /policies/label/logo
• /policies/label/logo_dark
• /policies/label/icon
• /policies/label/icon_dark
• /policies/label/font
• /text/message/passwordless_registration/{language}
• /text/login/{language}

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

Credit

This vulnerability was discovered by Amit Laish, a senior security researcher from GE Vernova and we want to thank him for reporting this to us!

The impact of this vulnerability varies depending on whether a ZITADEL instance utilizes LDAP for authentication:

• LDAP Users: Successful exploitation could lead to complete takeover of user accounts and exposure of the LDAP server's password.
• Non-LDAP Users: While the most severe risks are related to LDAP, exploitation of the additional vulnerable endpoints could still allow unauthorized modification of instance settings, impacting all organizations.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2025-27507 has a CVSS score of 9.0 (Critical). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.63.8, 2.64.5, 2.65.6, 2.66.11, 2.67.8, 2.68.4, 2.69.4, 2.70.1); upgrading removes the vulnerable code path.

Kodem intelligence

2.x versions are fixed on >= 2.71.0
2.70.x versions are fixed on >= 2.70.1
2.69.x versions are fixed on >= 2.69.4
2.68.x versions are fixed on >= 2.68.4
2.67.x versions are fixed on >= 2.67.8
2.66.x versions are fixed on >= 2.66.11
2.65.x versions are fixed on >= 2.65.6
2.64.x versions are fixed on >= 2.64.5
2.63.x versions are fixed on >= 2.63.8

1. What is CVE-2025-27507? CVE-2025-27507 is a critical-severity incorrect authorization vulnerability in github.com/zitadel/zitadel/v2 (go), affecting versions < 2.63.8. It is fixed in 2.63.8, 2.64.5, 2.65.6, 2.66.11, 2.67.8, 2.68.4, 2.69.4, 2.70.1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2025-27507? CVE-2025-27507 has a CVSS score of 9.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-27507?
   • github.com/zitadel/zitadel/v2 (go) (versions < 2.63.8)
   • github.com/zitadel/zitadel (go) (versions < 2.63.8)
4. Is there a fix for CVE-2025-27507? Yes. CVE-2025-27507 is fixed in 2.63.8, 2.64.5, 2.65.6, 2.66.11, 2.67.8, 2.68.4, 2.69.4, 2.70.1. Upgrade to this version or later.
5. Is CVE-2025-27507 exploitable, and should I be worried? Whether CVE-2025-27507 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-27507 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-27507?
   • Upgrade github.com/zitadel/zitadel/v2 to 2.63.8 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.64.5 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.65.6 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.66.11 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.67.8 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.68.4 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.69.4 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.70.1 or later
   • Upgrade github.com/zitadel/zitadel to 2.63.8 or later
   • Upgrade github.com/zitadel/zitadel to 2.64.5 or later
   • Upgrade github.com/zitadel/zitadel to 2.65.6 or later
   • Upgrade github.com/zitadel/zitadel to 2.66.11 or later
   • Upgrade github.com/zitadel/zitadel to 2.67.8 or later
   • Upgrade github.com/zitadel/zitadel to 2.68.4 or later
   • Upgrade github.com/zitadel/zitadel to 2.69.4 or later
   • Upgrade github.com/zitadel/zitadel to 2.70.1 or later