{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-94217 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-94217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-94217 is a low-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 21 Sep 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-94217 and fix it if it is affected.\n\nWhat it is: CVE-2026-94217 is a low-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 21 Sep 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-94217 in the wild and no public exploit code.\n\nAffected product: Red Hat Build of Keycloak. 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-2026-94217/ (Markdown: https://insights.sbomify.com/CVE-2026-94217/index.md)","id":"CVE-2026-94217","markdown":"https://insights.sbomify.com/CVE-2026-94217/index.md","name":"CVE-2026-94217","record":{"aliases":["GHSA-2cpw-3v2x-mh42"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"low_privilege","summary":"Attackers can gain unauthorized access to victim resources by exploiting name collisions in Keycloak's UMA permission ticket processing.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A flaw was found in the User-Managed Access (UMA) implementation of Keycloak. The issue occurs in the authorization token endpoint when processing permission tickets. If two different users own resources with the same name, the system incorrectly merges the permissions from both resources when one user requests an authorization token. This allows an attacker to gain access scopes on a victim's resource that were never intended to be shared.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision","id":"CVE-2026-94217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Keycloak-services: keycloak-services: 2fa setup enforcement bypass via authentication session restart endpoint","id":"CVE-2026-94218"},"packages":[],"prev":{"headline":"ST Engineering iDirect iDX/Evo iDX HTTP Request authorize response splitting","id":"CVE-2026-94216"},"products":["Red Hat Build of Keycloak","Red Hat Single Sign-On 7"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-24","vendors":["Red Hat"]},"summary":"Attackers can gain unauthorized access to victim resources by exploiting name collisions in Keycloak's UMA permission ticket processing.","url":"https://insights.sbomify.com/CVE-2026-94217/"}