{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-31124 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-31124 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-31124 is a medium-severity vulnerability in zitadel, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-31124 and fix it if it is affected.\n\nWhat it is: CVE-2025-31124 is a medium-severity vulnerability in zitadel, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-31124 in the wild and no public exploit code.\n\nAffected product: zitadel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-31124/ (Markdown: https://insights.sbomify.com/CVE-2025-31124/index.md)","id":"CVE-2025-31124","markdown":"https://insights.sbomify.com/CVE-2025-31124/index.md","name":"CVE-2025-31124","record":{"aliases":["GHSA-67m4-8g4w-633q"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity infrastructure software","requires_auth":"none","summary":"Attackers can enumerate valid usernames in Zitadel by exploiting username normalization flaws, even when the 'Ignoring unknown usernames' security setting is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zitadel","vendor":"zitadel"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"},{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Zitadel allows User Enumeration by loginname attribute normalization","id":"CVE-2025-31124","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":11,"next":{"headline":"Vite Vitejs Improper Access Control","id":"CVE-2025-31125"},"packages":[],"prev":{"headline":"Zitadel Expired JWT Keys Usable for Authorization Grants","id":"CVE-2025-31123"},"products":["zitadel"],"published":"2025-03-31","related":[{"cvss_score":9.3,"headline":"ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint","id":"CVE-2026-29191","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":9.3,"headline":"ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login","id":"CVE-2025-67494","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":9,"headline":"IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations","id":"CVE-2025-27507","kev_date_added":null,"published":"2025-03-04"},{"cvss_score":8.7,"headline":"Zitadel Bypass Second Authentication Factor","id":"CVE-2025-64103","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":8.7,"headline":"Zitadel Expired JWT Keys Usable for Authorization Grants","id":"CVE-2025-31123","kev_date_added":null,"published":"2025-03-31"},{"cvss_score":8.7,"headline":"ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass","id":"CVE-2024-29891","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":8.7,"headline":"XSS with User Avatar image in ZITADEL","id":"CVE-2023-46238","kev_date_added":null,"published":"2023-10-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-31","vendors":["zitadel"]},"summary":"Attackers can enumerate valid usernames in Zitadel by exploiting username normalization flaws, even when the 'Ignoring unknown usernames' security setting is enabled.","url":"https://insights.sbomify.com/CVE-2025-31124/"}