CVE-2024-46999

Workarounds

Unpatched versions can explicitly remove the user grants to make sure the user does not get access anymore.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

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.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2024-46999 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10); upgrading removes the vulnerable code path.

Kodem intelligence

2.x versions are fixed on >= 2.62.1
2.61.x versions are fixed on >= 2.61.1
2.60.x versions are fixed on >= 2.60.2
2.59.x versions are fixed on >= 2.59.3
2.58.x versions are fixed on >= 2.58.5
2.57.x versions are fixed on >= 2.57.5
2.56.x versions are fixed on >= 2.56.6
2.55.x versions are fixed on >= 2.55.8
2.54.x versions are fixed on >= 2.54.10

1. What is CVE-2024-46999? CVE-2024-46999 is a high-severity improper privilege management vulnerability in github.com/zitadel/zitadel/v2 (go), affecting versions >= 2.62.0, < 2.62.1. It is fixed in 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2024-46999? CVE-2024-46999 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/zitadel/zitadel/v2 are affected by CVE-2024-46999? github.com/zitadel/zitadel/v2 (go) versions >= 2.62.0, < 2.62.1 is affected.
4. Is there a fix for CVE-2024-46999? Yes. CVE-2024-46999 is fixed in 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10. Upgrade to this version or later.
5. Is CVE-2024-46999 exploitable, and should I be worried? Whether CVE-2024-46999 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-46999 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-46999?
   • Upgrade github.com/zitadel/zitadel/v2 to 2.62.1 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.61.1 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.60.2 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.59.3 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.58.5 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.57.5 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.56.6 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.55.8 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 2.54.10 or later