# 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. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 19 Sep 2024 - **Updated:** 20 Sep 2024 - **Also known as:** GHSA-jj94-6f5c-65r8, GO-2024-3138 ## 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. Weakness: CWE-863 (Incorrect Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## 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 | Ecosystem | 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 | | `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: 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. ## 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](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-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-47060 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2024-47060 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel/v2 (Go): affected all versions; fixed in 2.54.10 - github.com/zitadel/zitadel/v2 (Go): affected all versions; fixed in 2.54.10 - github.com/zitadel/zitadel/v2 (Go): affected from 2.55.0; fixed in 2.55.8 - github.com/zitadel/zitadel/v2 (Go): affected from 2.55.0; fixed in 2.55.8 - github.com/zitadel/zitadel/v2 (Go): affected from 2.56.0; fixed in 2.56.6 - github.com/zitadel/zitadel/v2 (Go): affected from 2.56.0; fixed in 2.56.6 - github.com/zitadel/zitadel/v2 (Go): affected from 2.57.0; fixed in 2.57.5 - github.com/zitadel/zitadel/v2 (Go): affected from 2.57.0; fixed in 2.57.5 - github.com/zitadel/zitadel/v2 (Go): affected from 2.58.0; fixed in 2.58.5 - github.com/zitadel/zitadel/v2 (Go): affected from 2.58.0; fixed in 2.58.5 - github.com/zitadel/zitadel/v2 (Go): affected from 2.59.0; fixed in 2.59.3 - github.com/zitadel/zitadel/v2 (Go): affected from 2.59.0; fixed in 2.59.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-2024-47060/ (Markdown: https://insights.sbomify.com/CVE-2024-47060/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47060 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47060 - OSV: https://osv.dev/vulnerability/CVE-2024-47060 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-47060/ Summaries are generated and may contain mistakes; the official description above is the record.