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

Zitadel Discloses the Total Number of Instance Users

Medium Go

Severity: 0.0 / 10; Medium · CVSS 4.0
Exploit chance (EPSS): 0.22%; Chance of exploitation in the next 30 days. Higher than 12.90% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
Fix: 4.7.2; Upgrade github.com/zitadel/zitadel to this version or later

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

Affected versions

Go

Package	Vulnerable	Fixed in
github.com/zitadel/zitadel	`>= 4.0.0-rc.1, < 4.7.2`	`4.7.2`
github.com/zitadel/zitadel	`>= 2.44.0, < 3.4.5`	`3.4.5`
github.com/zitadel/zitadel	`< 1.80.0-v2.20.0.20251210121356-826039c6208f`	`1.80.0-v2.20.0.20251210121356-826039c6208f`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/zitadel/zitadel Go → `4.7.2`

go

go get github.com/zitadel/zitadel@v4.7.2 && go mod tidy

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: Low
Attack requirements: None
Privileges required: Low
User interaction: None
Confidentiality (vulnerable system): Low
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Weakness

CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere

The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.

How to prevent it

Architecture and Design, Implementation: Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user. All error message text should be HTML entity encoded before being written to the log file to protect against potential cross-site scripting attacks against the viewer of the logs

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2025-67717

Packages

github.com/zitadel/zitadel

Timeline

Dec 10, 2025 Published
Oct 14, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-fgmf-7rf8-m6vf ZITADEL: Actions V1 sandbox escape: host file read via require()	High	Also affects github.com/zitadel/zitadel
GHSA-9993-rfwp-rhwf ZITADEL: MFA bypass via session reuse in Login V2	High	Also affects github.com/zitadel/zitadel
GHSA-v859-c572-qh5p ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions	Medium	Also affects github.com/zitadel/zitadel
GHSA-jq8w-8q2f-ffm9 ZITADEL Users Can Self-Verify Email/Phone via API	High	Also affects github.com/zitadel/zitadel
GHSA-vrh8-c9cm-wh8v ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange	High	Also affects github.com/zitadel/zitadel
GHSA-992q-9gwp-7r79 ZITADEL: Auto-linking by email: IdP-side email verification is not checked	Medium	Also affects github.com/zitadel/zitadel
GHSA-v77h-2w3m-94hx ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider	Medium	Also affects github.com/zitadel/zitadel
GHSA-g5h5-m4hm-xjrr ZITADEL: Missing Token Audience Validation (`aud`) in JWT IdP Provider	Medium	Also affects github.com/zitadel/zitadel

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor