CVE-2024-47060
MEDIUMUnauthorized Access After Organization or Project Deactivation in Zitadel
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.62.0&&< 2.62.1 | 2.62.1 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.61.0&&< 2.61.1 | 2.61.1 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.60.0&&< 2.60.2 | 2.60.2 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.59.0&&< 2.59.3 | 2.59.3 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.58.0&&< 2.58.5 | 2.58.5 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.57.0&&< 2.57.5 | 2.57.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/zitadel/zitadel/v2 to 2.62.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47060 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-47060 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-47060. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-47060 in your dependencies?
O3 detects CVE-2024-47060 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.