{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-57770 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-57770 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-57770 is a medium-severity vulnerability in zitadel, published on 22 Aug 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-57770 and fix it if it is affected.\n\nWhat it is: CVE-2025-57770 is a medium-severity vulnerability in zitadel, published on 22 Aug 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-57770 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-57770/ (Markdown: https://insights.sbomify.com/CVE-2025-57770/index.md)","id":"CVE-2025-57770","markdown":"https://insights.sbomify.com/CVE-2025-57770/index.md","name":"CVE-2025-57770","record":{"aliases":["GHSA-g9c3-xh6v-fr86"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity infrastructure software","requires_auth":"none","summary":"An unauthenticated attacker can enumerate valid user accounts by bypassing the login UI's unknown username protection, exposing user existence.","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-203","name":"Observable Discrepancy"}],"description":"The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. Versions 4.0.0 to 4.0.2, 3.0.0 to 3.3.6, and all versions prior to 2.71.15 are vulnerable to a username enumeration issue in the login interface. The login UI includes a security feature, Ignoring unknown usernames, that is intended to prevent username enumeration by returning a generic response for both valid and invalid usernames. This vulnerability allows an unauthenticated attacker to bypass this protection by submitting arbitrary userIDs to the select account page and distinguishing between valid and invalid accounts based on the system's response. For effective exploitation, an attacker needs to iterate through possible userIDs, but the impact can be limited by implementing rate limiting or similar measures. The issue has been patched in versions 4.0.3, 3.4.0, and 2.71.15.","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 user enumeration vulnerability in login UI","id":"CVE-2025-57770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Roo-Code potential remote code execution via auto-execute command parsing flaw","id":"CVE-2025-57771"},"packages":[],"prev":{"headline":"FressRSS: Clickjacking can lead to XSS and/or privilege escalation","id":"CVE-2025-57769"},"products":["zitadel"],"published":"2025-08-22","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-22","vendors":["zitadel"]},"summary":"An unauthenticated attacker can enumerate valid user accounts by bypassing the login UI's unknown username protection, exposing user existence.","url":"https://insights.sbomify.com/CVE-2025-57770/"}