CVE-2025-27507: IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations
Summary
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/logodark - /policies/label/icon - /policies/label/icondark - /policies/label/font - /text/message/passwordlessregistration/{language} - /text/login/{language}
Impact
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.
Patches
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
Questions
If you have any questions or comments about this advisory, please email us at security@zitadel.com
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!
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.70.1 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.69.4 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.68.4 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.67.8 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.66.11 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.65.6 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.64.5 - Upgrade
Upgrade
go/github.com/zitadel/zitadelto a version that resolves this vulnerability.Fixed in 2.63.8 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.70.1 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.69.4 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.68.4 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.67.8 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.66.11 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.65.6 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.64.5 - Upgrade
Upgrade
go/github.com/zitadel/zitadel/v2to a version that resolves this vulnerability.Fixed in 2.63.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.63.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.64.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.65.6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.66.11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.67.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.68.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.69.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.70.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.71.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-27507?
CVE-2025-27507 is classified as a critical vulnerability due to the potential impact of unauthorized modification of sensitive settings.
How do I fix CVE-2025-27507?
To remediate CVE-2025-27507, upgrade to ZITADEL version 2.70.1 or later.
What specific settings can be modified due to CVE-2025-27507?
CVE-2025-27507 allows unauthorized authenticated users to modify sensitive settings through the Admin API endpoints.
Which versions of ZITADEL are affected by CVE-2025-27507?
Affected versions of ZITADEL include all versions prior to 2.70.1.
What type of vulnerability is CVE-2025-27507?
CVE-2025-27507 is categorized as an Insecure Direct Object Reference (IDOR) vulnerability.