ZITADEL's User Grant Deactivation not WorkingGHSA-2w5j-qfvw-2hf5
HIGHGHSA-2w5j-qfvw-2hf5 is a high-severity (CVSS 7.3) Improper Privilege Management vulnerability in github.com/zitadel/zitadel/v2. A fix is available for github.com/zitadel/zitadel/v2 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2w5j-qfvw-2hf5.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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
Impact
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.
Patches
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
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]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.62.0&&< 2.62.1 | 2.62.1go get github.com/zitadel/zitadel/v2@v2.62.1 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.61.0&&< 2.61.1 | 2.61.1go get github.com/zitadel/zitadel/v2@v2.61.1 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.60.0&&< 2.60.2 | 2.60.2go get github.com/zitadel/zitadel/v2@v2.60.2 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.59.0&&< 2.59.3 | 2.59.3go get github.com/zitadel/zitadel/v2@v2.59.3 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.58.0&&< 2.58.5 | 2.58.5go get github.com/zitadel/zitadel/v2@v2.58.5 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.57.0&&< 2.57.5 | 2.57.5go get github.com/zitadel/zitadel/v2@v2.57.5 |
Affected Products
zitadelzitadelDetection & 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 GHSA-2w5j-qfvw-2hf5 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-2w5j-qfvw-2hf5 in your dependencies?
Find it across Go, including transitive dependencies.