CVE-2024-47060 Unauthorized Access After Organization or Project Deactivation in Zitadel
Attackers can access deactivated organization projects and applications, leading to unauthorized data exposure and security bypass in Zitadel.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-47060?
CVE-2024-47060 is a medium-severity missing authorization vulnerability in zitadel, published on 19 Sep 2024. 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. In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible. The issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, leading to a situation where the organization or project is marked as inactive, but its resources remain accessible. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised to upgrade. Users unable to upgrade may explicitly disable the application to make sure the client is not allowed anymore.
Which versions are affected by CVE-2024-47060?
19 open source packages ship an affected version, including github.com/zitadel/zitadel/v2 and github.com/zitadel/zitadel. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/zitadel/zitadel/v2 Go | All versions | 2.54.10 |
github.com/zitadel/zitadel/v2 Go | All versions | 2.54.10 |
github.com/zitadel/zitadel/v2 Go | From 2.55.0 | 2.55.8 |
github.com/zitadel/zitadel/v2 Go | From 2.55.0 | 2.55.8 |
github.com/zitadel/zitadel/v2 Go | From 2.56.0 | 2.56.6 |
github.com/zitadel/zitadel/v2 Go | From 2.56.0 | 2.56.6 |
13 more packages
github.com/zitadel/zitadel/v2 Go | From 2.57.0 | 2.57.5 |
github.com/zitadel/zitadel/v2 Go | From 2.57.0 | 2.57.5 |
github.com/zitadel/zitadel/v2 Go | From 2.58.0 | 2.58.5 |
github.com/zitadel/zitadel/v2 Go | From 2.58.0 | 2.58.5 |
github.com/zitadel/zitadel/v2 Go | From 2.59.0 | 2.59.3 |
github.com/zitadel/zitadel/v2 Go | From 2.59.0 | 2.59.3 |
github.com/zitadel/zitadel/v2 Go | From 2.60.0 | 2.60.2 |
github.com/zitadel/zitadel/v2 Go | From 2.60.0 | 2.60.2 |
github.com/zitadel/zitadel/v2 Go | From 2.61.0 | 2.61.1 |
github.com/zitadel/zitadel/v2 Go | From 2.61.0 | 2.61.1 |
github.com/zitadel/zitadel/v2 Go | From 2.62.0 | 2.62.1 |
github.com/zitadel/zitadel/v2 Go | From 2.62.0 | 2.62.1 |
github.com/zitadel/zitadel Go | All versions | None |
Products include Zitadel Zitadel.
How do I fix CVE-2024-47060?
Upgrade github.com/zitadel/zitadel/v2 to a fixed version for your release line: 2.54.10, 2.55.8, 2.56.6 or 2.57.5.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-47060 being exploited?
There is no known exploitation of CVE-2024-47060 in the wild and no public exploit code.
Other vulnerabilities in zitadel
- CVE-2026-29191 ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint
- CVE-2025-67494 ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login
- CVE-2025-27507 IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations
- CVE-2025-64103 Zitadel Bypass Second Authentication Factor
- CVE-2025-31123 Zitadel Expired JWT Keys Usable for Authorization Grants
Sources
Also known as GHSA-jj94-6f5c-65r8, GO-2024-3138.