{"answers":{"affected":"3 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3872 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-services to 26.5.7 or later.","what":"CVE-2026-3872 is a high-severity vulnerability in Redhat Build of Keycloak, published on 2 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-3872 and fix it if it is affected.\n\nWhat it is: CVE-2026-3872 is a high-severity vulnerability in Redhat Build of Keycloak, published on 2 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-3872 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.5.7\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.5.7\n- keycloak (Bitnami): affected from 26.2.0; fixed in 26.2.1, 26.3.0, 26.4.1, 26.5.0\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-2026-3872/ (Markdown: https://insights.sbomify.com/CVE-2026-3872/index.md)","id":"CVE-2026-3872","markdown":"https://insights.sbomify.com/CVE-2026-3872/index.md","name":"CVE-2026-3872","record":{"aliases":["BIT-keycloak-2026-3872","ECHO-cc7d-8394-7880","GHSA-cjm2-j6cm-6p6m","MINI-69xr-mhqw-p2m5","MINI-8f53-4v69-q7cx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"low_privilege","summary":"Attackers can bypass redirect URI validation to steal access tokens, leading to information disclosure and potential account takeover in Keycloak deployments.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_keycloak","vendor":"redhat"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"A flaw was found in Keycloak. This issue allows an attacker, who controls another path on the same web server, to bypass the allowed path in redirect Uniform Resource Identifiers (URIs) that use a wildcard. A successful attack may lead to the theft of an access token, resulting in information disclosure.","ecosystems":["Bitnami","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: keycloak: information disclosure due to redirect_uri validation bypass","id":"CVE-2026-3872","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"redhat:build_of_keycloak","products":["redhat:build_of_keycloak"],"type":"open_redirect","year":"2026"},"n_packages":3,"n_references":6,"next":{"headline":"Legacy built-in user account","id":"CVE-2026-3873"},"packages":[{"ecosystem":"Bitnami","fixed":["26.2.1","26.3.0","26.4.1","26.5.0"],"introduced":["26.2.0","26.2.15","26.4.0","26.4.11"],"last_affected":[],"package":"keycloak","purl":"pkg:bitnami/keycloak","source":"BIT-keycloak-2026-3872"},{"ecosystem":"Maven","fixed":["26.5.7"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-cjm2-j6cm-6p6m"},{"ecosystem":"Maven","fixed":["26.5.7"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-cjm2-j6cm-6p6m"}],"prev":{"headline":"Memory corruption in VMG4005-B50B firmware","id":"CVE-2026-3871"},"products":["Red Hat build of Keycloak 26.2","Red Hat build of Keycloak 26.2.15","Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.11"],"published":"2026-04-02","related":[{"cvss_score":8.8,"headline":"Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation","id":"CVE-2026-15572","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.8,"headline":"Keycloak SAML Broken has Authentication Bypass by Primary Weakness","id":"CVE-2026-3047","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.1,"headline":"Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher","id":"CVE-2026-15573","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.1,"headline":"Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers","id":"CVE-2026-16102","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.1,"headline":"Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users","id":"CVE-2026-1609","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":8.1,"headline":"Org.keycloak:keycloak-services: keycloak: authentication bypass via jwt algorithm confusion","id":"CVE-2026-11800","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":8.1,"headline":"Keycloak-policy-enforcer: keycloak policy enforcer: authorization bypass via incorrect uri comparison","id":"CVE-2026-9800","kev_date_added":null,"published":"2026-06-25"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"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":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["Red Hat"]},"summary":"Attackers can bypass redirect URI validation to steal access tokens, leading to information disclosure and potential account takeover in Keycloak deployments.","url":"https://insights.sbomify.com/CVE-2026-3872/"}