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

Zitadel Discloses the Total Number of Instance UsersGHSA-f4cf-9rvr-2rcx

MEDIUMFix: zitadel/zitadel@826039c

GHSA-f4cf-9rvr-2rcx is a medium-severity (CVSS 4.3) CWE-497 vulnerability in github.com/zitadel/zitadel. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below.

Also known asCVE-2025-67717GO-2025-4227
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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-f4cf-9rvr-2rcx.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk
0.00%0.24%0.48%0.72%0.0%0.2%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

3 pkgs affected
🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel

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

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

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/zitadel/zitadel≥ 4.0.0-rc.1&&< 4.7.24.7.2go get github.com/zitadel/zitadel@v4.7.2
🐹Gogithub.com/zitadel/zitadel≥ 2.44.0&&< 3.4.53.4.5go get github.com/zitadel/zitadel@v3.4.5
🐹Gogithub.com/zitadel/zitadelall versions1.80.0-v2.20.0.20251210121356-826039c6208fgo get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251210121356-826039c6208f

Affected Products

1 product · 3 configurations
Application
zitadelzitadel
≥ 4.0.0 && ≤ 2.71.19
range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/zitadel/zitadel to 4.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4cf-9rvr-2rcx is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### 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` - *
O3 Security · Impact-Aware SCA

Is GHSA-f4cf-9rvr-2rcx in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Zitadel Discloses the Total Number of Instance Users