CVE-2025-67717

CVE-2025-67717 is a medium-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 4.0.0-rc.1, <= 4.7.1. It is fixed in 4.7.2, 3.4.5, 1.80.0-v2.20.0.20251210121356-826039c6208f.

Summary

Zitadel's User Service discloses the total number of instance users to unauthorized users.

Affected Versions

Systems running one of the following version are affected:

  • 4.x: 4.0.0-rc.1 through 4.7.1
  • 3.x: 3.0.0-rc.1 through 3.4.4
  • 2.x: 2.44.0 through 2.71.19

Workarounds

The recommended solution is to update Zitadel to a patched version.

If a version upgrade is not possible, you can enable the permissionCheckV2 feature on your instance.

Questions

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

Credits

This vulnerability was found by zentrust partners GmbH during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann.
The full report will be made public after the complete review.

Impact

The ZITADEL User Service exposes the total number of users within an instance to any authenticated user, regardless of their specific permissions. While this does not leak individual user data or PII, disclosing the total user count via the totalResult field constitutes an information disclosure vulnerability that may be sensitive in certain contexts.

CVE-2025-67717 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. 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 (4.7.2, 3.4.5, 1.80.0-v2.20.0.20251210121356-826039c6208f); upgrading removes the vulnerable code path.

Affected versions

github.com/zitadel/zitadel (>= 4.0.0-rc.1, <= 4.7.1) github.com/zitadel/zitadel (>= 2.44.0, <= 3.4.4) github.com/zitadel/zitadel (< 1.80.0-v2.20.0.20251210121356-826039c6208f)

Security releases

github.com/zitadel/zitadel → 4.7.2 (go) github.com/zitadel/zitadel → 3.4.5 (go) github.com/zitadel/zitadel → 1.80.0-v2.20.0.20251210121356-826039c6208f (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

The vulnerability has been addressed in the latest release. The patch resolves the issue and returns the totalResult value corresponding to the number of instance users for whom the querying user has read permission.

  • 4.x: Upgrade to >= 4.7.2
  • 3.x: Update to >= 3.4.5
  • 2.x: Update to >= 3.4.5 (or checkout the workarounds section)

Frequently Asked Questions

  1. What is CVE-2025-67717? CVE-2025-67717 is a medium-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 4.0.0-rc.1, <= 4.7.1. It is fixed in 4.7.2, 3.4.5, 1.80.0-v2.20.0.20251210121356-826039c6208f.
  2. How severe is CVE-2025-67717? CVE-2025-67717 has a CVSS score of 4.3 (Medium). 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 are affected by CVE-2025-67717? github.com/zitadel/zitadel (go) versions >= 4.0.0-rc.1, <= 4.7.1 is affected.
  4. Is there a fix for CVE-2025-67717? Yes. CVE-2025-67717 is fixed in 4.7.2, 3.4.5, 1.80.0-v2.20.0.20251210121356-826039c6208f. Upgrade to this version or later.
  5. Is CVE-2025-67717 exploitable, and should I be worried? Whether CVE-2025-67717 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-2025-67717 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-2025-67717?
    • Upgrade github.com/zitadel/zitadel to 4.7.2 or later
    • Upgrade github.com/zitadel/zitadel to 3.4.5 or later
    • Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251210121356-826039c6208f or later

Other vulnerabilities in github.com/zitadel/zitadel

CVE-2026-55669CVE-2026-55672CVE-2026-55670CVE-2026-55671CVE-2026-44671

Stop the waste.
Protect your environment with Kodem.