NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2024-47000 — zitadel

HIGH

CVE-2024-47000 is a high-severity (CVSS 8.1) 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.

Service Users Deactivation not Working in Zitadel

Also known asGHSA-qr2h-7pwm-h393GO-2024-3139
Published
Updated
Affected
9 pkgs
Patched
9 / 9
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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 CVE-2024-47000.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk
0.00%0.30%0.61%0.91%0.2%0.4%May 26Sep 26Nov 26

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

9 pkgs affected
🐹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 more

Real-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 account deactivation mechanism did not work correctly with service accounts. Deactivated service accounts retained the ability to request tokens, which could lead to unauthorized access to applications and resources.

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

Instead of deactivating the service account, consider creating new credentials and replacing the old ones wherever they are used. This effectively prevents the deactivated service account from being utilized.

  • Revoke all existing authentication keys associated with the service account
  • Rotate the service account's password

Questions

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

[email protected]

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/zitadel/zitadel/v2≥ 2.62.0&&< 2.62.12.62.1go get github.com/zitadel/zitadel/v2@v2.62.1
🐹Gogithub.com/zitadel/zitadel/v2≥ 2.61.0&&< 2.61.12.61.1go get github.com/zitadel/zitadel/v2@v2.61.1
🐹Gogithub.com/zitadel/zitadel/v2≥ 2.60.0&&< 2.60.22.60.2go get github.com/zitadel/zitadel/v2@v2.60.2
🐹Gogithub.com/zitadel/zitadel/v2≥ 2.59.0&&< 2.59.32.59.3go get github.com/zitadel/zitadel/v2@v2.59.3
🐹Gogithub.com/zitadel/zitadel/v2≥ 2.58.0&&< 2.58.52.58.5go get github.com/zitadel/zitadel/v2@v2.58.5
🐹Gogithub.com/zitadel/zitadel/v2≥ 2.57.0&&< 2.57.52.57.5go get github.com/zitadel/zitadel/v2@v2.57.5

Affected Products

1 product · 9 configurations
Application
zitadelzitadel
≥ 2.60.0 && < 2.60.2
2 versions
2.61.02.62.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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-47000 is resolved across your whole dependency graph.

  3. 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

### Impact ZITADEL's user account deactivation mechanism did not work correctly with service accounts. Deactivated service accounts retained the ability to request tokens, which could lead to unauthorized access to applications and resources. ### Patches 2.x versions are fixed on >= [2.62.1](https://github.com/zitadel/zitadel/releases/tag/v2.62.1) 2.61.x versions are fixed on >= [2.61.1](https://github.com/zitadel/zitadel/releases/tag/v2.61.1) 2.60.x versions are fixed on >= [2.60.2](https://github.com/zitadel/zitadel/releases/tag/v2.60.2) 2.59.x versions are fixed on >= [2.59.3](https://git
O3 Security · Impact-Aware SCA

Is CVE-2024-47000 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-47000: zitadel — Fixed in 2.62.1