CVE-2024-46999 User Grant Deactivation not Working in Zitadel
Attackers can retain unauthorized access to applications and resources because deactivated user grants were still included in tokens.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2024-46999?
CVE-2024-46999 is a high-severity authentication bypass vulnerability in zitadel, published on 19 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Zitadel is an open source identity management platform. ZITADEL's user grants deactivation mechanism did not work correctly. Deactivated user grants were still provided in token, which could lead to unauthorized access to applications and resources. Additionally, the management and auth API always returned the state as active or did not provide any information about the state. 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 remove the user grants to make sure the user does not get access anymore.
Weakness: CWE-269
Which versions are affected by CVE-2024-46999?
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-46999?
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 rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2024-46999 being exploited?
There is no known exploitation of CVE-2024-46999 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-2w5j-qfvw-2hf5, GO-2024-3137.