CVE-2025-31124 json
Zitadel allows User Enumeration by loginname attribute normalization
published last yr. modified 4mo ago also EUVD-2025-8871
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Zitadel is open-source identity infrastructure software. ZITADEL administrators can enable a setting called "Ignoring unknown usernames" which helps mitigate attacks that try to guess/enumerate usernames. If enabled, ZITADEL will show the password prompt even if the user doesn't exist and report "Username or Password invalid". While the setting was correctly respected during the login flow, the user's username was normalized leading to a disclosure of the user's existence. This vulnerability is fixed in 2.71.6, 2.70.8, 2.69.9, 2.68.9, 2.67.13, 2.66.16, 2.65.7, 2.64.6, and 2.63.9.
Patch / fix
- zitadel zitadel 2.63.9, 2.64.6, 2.65.7, 2.66.16, 2.67.13, 2.68.9, 2.69.9, 2.70.8, 2.71.6
- github.com/zitadel/zitadel@14de8ec commit
- github.com/zitadel/zitadel/releases/tag/v2.63.9 release
- github.com/zitadel/zitadel/releases/tag/v2.64.6 release
- github.com/zitadel/zitadel/releases/tag/v2.65.7 release
- github.com/zitadel/zitadel/releases/tag/v2.66.16 release
- github.com/zitadel/zitadel/releases/tag/v2.67.13 release
- github.com/zitadel/zitadel/releases/tag/v2.68.9 release
- github.com/zitadel/zitadel/releases/tag/v2.69.9 release
- github.com/zitadel/zitadel/releases/tag/v2.70.8 release
- github.com/zitadel/zitadel/releases/tag/v2.71.6 release
Is CVE-2025-31124 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- zitadel zitadel
Classification
References
-
github.com
/zitadel/zitadel/commit/14de8ecac2afafee4975ed7ac26f3ca4a2b0f82c
patch
-
github.com
/zitadel/zitadel/security/advisories/GHSA-67m4-8g4w-633q
vendor-advisory
-
github.com
/zitadel/zitadel/releases/tag/v2.63.9
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.64.6
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.65.7
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.66.16
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.67.13
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.68.9
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.69.9
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.70.8
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v2.71.6
release-notes
Sources
- CVE List CVE-2025-31124
- NVD CVE-2025-31124
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.