CVE-2024-47060

Unauthorized Access After Organization or Project Deactivation in Zitadel

MEDIUM
6.5
CVSS Score
Published: September 19, 2024 at 11:08 PM UTC
Updated: June 17, 2026 at 07:56 AM UTC
1 product affected across 1 vendorZitadel

Using zitadel by zitadel?

Get instant alerts when new vulnerabilities affect zitadel - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.54.10v < 2.55.8v < 2.56.6v < 2.57.5v < 2.58.5v < 2.59.3v < 2.60.2v < 2.61.1v < 2.62.12.55.0 ≤ v < 2.55.82.56.0 ≤ v < 2.56.62.57.0 ≤ v < 2.57.52.58.0 ≤ v < 2.58.52.59.0 ≤ v < 2.59.32.60.0 ≤ v < 2.60.22.61.02.62.0
Affected range stops below 2.54.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.55.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.56.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.57.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.58.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.59.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.60.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.61.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.62.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card