{"answers":{"affected":"4 open source packages ship an affected version, including org.keycloak:keycloak-ldap-federation.","exploited":"There is no known exploitation of CVE-2025-0604 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-ldap-federation to a fixed version for your release line: 26.0.10 or 26.1.3.","what":"CVE-2025-0604 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 22 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0604 and fix it if it is affected.\n\nWhat it is: CVE-2025-0604 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 22 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-0604 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-ldap-federation (Maven): affected all versions; fixed in 26.0.10\n- org.keycloak:keycloak-ldap-federation (Maven): affected all versions; fixed in 26.0.10\n- org.keycloak:keycloak-ldap-federation (Maven): affected from 26.1.0; fixed in 26.1.3\n- org.keycloak:keycloak-ldap-federation (Maven): affected from 26.1.0; fixed in 26.1.3\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-0604/ (Markdown: https://insights.sbomify.com/CVE-2025-0604/index.md)","id":"CVE-2025-0604","markdown":"https://insights.sbomify.com/CVE-2025-0604/index.md","name":"CVE-2025-0604","record":{"aliases":["ECHO-0030-65ec-f55d","GHSA-2p82-5wwr-43cw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity and Access Management","requires_auth":"low_privilege","summary":"Attackers can bypass Active Directory restrictions to regain access to Keycloak accounts after password resets, potentially leading to unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"A flaw was found in Keycloak. When an Active Directory user resets their password, the system updates it without performing an LDAP bind to validate the new credentials against AD. This vulnerability allows users whose AD accounts are expired or disabled to regain access in Keycloak, bypassing AD restrictions. The issue enables authentication bypass and could allow unauthorized access under certain conditions.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Keycloak-ldap-federation: authentication bypass due to missing ldap bind after password reset in keycloak","id":"CVE-2025-0604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":4,"n_references":4,"next":{"headline":"Weak Authentication in GitLab","id":"CVE-2025-0605"},"packages":[{"ecosystem":"Maven","fixed":["26.0.10"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-ldap-federation","purl":null,"source":"GHSA-2p82-5wwr-43cw"},{"ecosystem":"Maven","fixed":["26.0.10"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-ldap-federation","purl":"pkg:maven/org.keycloak/keycloak-ldap-federation","source":"GHSA-2p82-5wwr-43cw"},{"ecosystem":"Maven","fixed":["26.1.3"],"introduced":["26.1.0"],"last_affected":[],"package":"org.keycloak:keycloak-ldap-federation","purl":null,"source":"GHSA-2p82-5wwr-43cw"},{"ecosystem":"Maven","fixed":["26.1.3"],"introduced":["26.1.0"],"last_affected":[],"package":"org.keycloak:keycloak-ldap-federation","purl":"pkg:maven/org.keycloak/keycloak-ldap-federation","source":"GHSA-2p82-5wwr-43cw"}],"prev":{"headline":"SQLi in Callvision Healthcare's Callvision Emergency Code","id":"CVE-2025-0603"},"products":["Red Hat Build of Keycloak","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26.0"],"published":"2025-01-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2026-10-13","vendors":["Red Hat"]},"summary":"Attackers can bypass Active Directory restrictions to regain access to Keycloak accounts after password resets, potentially leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-0604/"}