MediumGHSA-f4cf-9rvr-2rcxCVE-2025-67717GO-2025-4227

Zitadel Discloses the Total Number of Instance Users

Published 10 Dec 2025 · Updated 3 Feb 2026

Is your project on an affected github.com/zitadel/zitadel?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.0.0-rc.1 <4.7.2
Fixed in
4.7.2
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v4.7.2
Affected
>=2.44.0 <3.4.5
Fixed in
3.4.5
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v3.4.5
Affected
<1.80.0-v2.20.0.20251210121356-826039c6208f
Fixed in
1.80.0-v2.20.0.20251210121356-826039c6208f
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251210121356-826039c6208f

Details

Summary

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

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.

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

Patches

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)

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 [security@zitadel.com](mailto:security@zitadel.com)

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.

Is GHSA-f4cf-9rvr-2rcx in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/zitadel/zitadel, and gives you the command that fixes it.

More advisories for github.com/zitadel/zitadel

  • LowCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 in github.com/zitadel/zitadel · 1 Oct 2026
  • LowCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() in github.com/zitadel/zitadel · 1 Oct 2026
  • HighCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 · 24 Sept 2026
  • HighCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() · 24 Sept 2026
  • LowCVE-2026-56665ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider in github.com/zitadel/zitadel · 16 Sept 2026
  • LowCVE-2026-56666ZITADEL: Auto-linking by email: IdP-side email verification is not checked in github.com/zitadel/zitadel · 16 Sept 2026
All 93 advisories for github.com/zitadel/zitadel

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.