# CVE-2025-67717: GO-2025-4227 - Zitadel Discloses the Total Number of Instance Users in github.com/zitadel/zitadel

Source: https://junglewise.ai/threats/cve-2025-67717-zitadel-discloses-the-total-number-of-instance-users  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-12-11  
License: CC BY 4.0 with a link back

CVE-2025-67717 · Severity: medium · CVSS 4.3 · Published 2025-12-11

ZITADEL is an open-source identity infrastructure tool. Versions 2.44.0 through 3.4.4 and 4.0.0-rc.1 through 4.7.1 disclose the total number of instance users to authenticated users, 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. This issue is fixed in versions 3.4.5 and 4.7.2.

Technologies: [github.com/zitadel/zitadel (Go)](https://junglewise.ai/threats/technologies/github-com-zitadel-zitadel), [ZITADEL](https://junglewise.ai/threats/technologies/zitadel). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [ZITADEL](https://junglewise.ai/threats/vendors/zitadel).

## Quick answers

**Is CVE-2025-67717 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-67717 being exploited in the wild.

**How severe is CVE-2025-67717?** Medium severity, with a CVSS score of 4.3, published 11 December 2025.

**Which products and versions are affected?** github.com/zitadel/zitadel (Go) SEMVER:introduced=0,fixed=1.80.0-v2.20.0.20251210121356-826039c6208f, SEMVER:introduced=4.0.0-rc.1,fixed=4.7.2.

**Is there a fix for CVE-2025-67717?** Yes. github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20251210121356-826039c6208f, 4.7.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-67717?** Check whether you run github.com/zitadel/zitadel (Go) or ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20251210121356-826039c6208f, 4.7.2 or later

  ```sh
  go get github.com/zitadel/zitadel@v4.7.2
  ```


## Affected products

- github.com/zitadel/zitadel (Go) SEMVER:introduced=0,fixed=1.80.0-v2.20.0.20251210121356-826039c6208f, SEMVER:introduced=4.0.0-rc.1,fixed=4.7.2
- ZITADEL

## Identifiers

- CVE-2025-67717
- GHSA-f4cf-9rvr-2rcx
- GO-2025-4227

## Related threats

- [ZITADEL missing authorization in Login V2 device authorization](https://junglewise.ai/threats/cve-2026-119129-zitadel-3-0-0-through-3-4-15-and-4-0-0-before-4-19-5-contains-a)
- [ZITADEL authentication bypass in Login V2 UI](https://junglewise.ai/threats/cve-2026-119128-zitadel-4-0-0-before-4-19-5-contains-an-authentication-bypass)
- [ZITADEL Login V2 host header injection in password reset](https://junglewise.ai/threats/cve-2026-119127-zitadel-4-0-0-before-4-19-5-contains-a-host-header-injection)
- [ZITADEL privilege escalation in OIDC token exchange](https://junglewise.ai/threats/cve-2026-109374-zitadel-3-0-0-before-4-19-2-contains-a-privilege-escalation)
- [ZITADEL authentication bypass in Login V2 UI](https://junglewise.ai/threats/cve-2026-109373-zitadel-3-0-0-before-4-19-2-contains-an-authentication-bypass)