{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2025-3501 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-services to 26.2.2 or later.","what":"CVE-2025-3501 is a high-severity vulnerability in Red Hat Build of Keycloak, published on 29 Apr 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-3501 and fix it if it is affected.\n\nWhat it is: CVE-2025-3501 is a high-severity vulnerability in Red Hat Build of Keycloak, published on 29 Apr 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-3501 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.2\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.2\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-3501/ (Markdown: https://insights.sbomify.com/CVE-2025-3501/index.md)","id":"CVE-2025-3501","markdown":"https://insights.sbomify.com/CVE-2025-3501/index.md","name":"CVE-2025-3501","record":{"aliases":["ECHO-32d8-b09c-5c73","GHSA-hw58-3793-42gg"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak identity server","requires_auth":"none","summary":"Attackers can bypass certificate verification in Keycloak by configuring a specific verification policy, potentially enabling man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is skipped, which is unintended.","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":"Org.keycloak.protocol.services: keycloak hostname verification","id":"CVE-2025-3501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":2,"n_references":8,"next":{"headline":"WP Maps \u003c 4.7.2 - Admin+ Stored XSS","id":"CVE-2025-3502"},"packages":[{"ecosystem":"Maven","fixed":["26.2.2"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-hw58-3793-42gg"},{"ecosystem":"Maven","fixed":["26.2.2"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-hw58-3793-42gg"}],"prev":{"headline":"Integer Overflow in Avast Antiviurs 25.1.981.6 on Windows may result in privilege escalation","id":"CVE-2025-3500"},"products":["Red Hat Build of Keycloak","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26","Red Hat build of Keycloak 26.0","Red Hat build of Keycloak 26.2"],"published":"2025-04-29","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["Red Hat"]},"summary":"Attackers can bypass certificate verification in Keycloak by configuring a specific verification policy, potentially enabling man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2025-3501/"}