{"id":"CVE-2026-94217","aliases":[],"summary":"Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision","published_at":"2026-09-19T23:39:17Z","modified_at":"2026-11-06T10:26:26.249Z","products":[],"rating":{"severity":"low","score":3.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","attack_path":"internet_authenticated","user_interaction":true,"malicious":false,"red_hat":"Moderate","vendor_ratings":[{"source":"Red Hat","rating":"Moderate"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.0029299999587237835,"percentile":0.22259999811649323,"date":"2026-11-19T00:00:00Z"},"priority":4,"details":"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.","affected_stack":[],"affected_other":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat Single Sign-On 7","cpe":"cpe:/a:redhat:red_hat_single_sign_on:7","status":"not_affected","packages":["keycloak-services"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-94217"},{"vendor":"Red Hat","product":"Red Hat build of Keycloak 26.6.8","cpe":"cpe:/a:redhat:build_keycloak:26.6::el9","status":"fixed","packages":[],"package_count":0,"fixed":[],"advisories":["RHSA-2026:95761"],"provider":"redhat-vex","source":"CVE-2026-94217"}],"records":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-3484","relation":"upstream","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3484","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-09-20T22:00:00Z","modified_at":"2026-11-08T23:00:00Z","summary":"Keycloak: Mehrere Schwachstellen","details":"Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Keycloak ausnutzen, um seine Privilegien zu erhöhen, um Sicherheitsmechanismen zu umgehen und um Informationen offenzulegen.\n\nKeycloak ermöglicht Single Sign-On mit Identity and Access Management für moderne Anwendungen und Dienste.","severity":[{"type":"BSI","score":"mittel","source":"WID-SEC-W-2026-3484"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-3484.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3484"},{"type":"WEB","url":"https://github.com/advisories/GHSA-82wc-7jr6-wxgm"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537165"},{"type":"WEB","url":"https://github.com/advisories/GHSA-3g7j-6fqv-v2q4"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537168"},{"type":"WEB","url":"https://github.com/advisories/GHSA-p353-3p63-7h28"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537169"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537310"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537312"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537313"},{"type":"WEB","url":"https://access.redhat.com/security/cve/cve-2026-94218"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:95761"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:95762"}]},{"provider":"cvelistv5","source_id":"CVE-2026-94217","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-94217","license":"CC-BY-4.0","published_at":"2026-09-21T06:45:27.795Z","modified_at":"2026-11-06T10:26:26.249Z","summary":"Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","source":"CVE-2026-94217"}],"affected":[],"product_status":[],"references":[{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:95761"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-94217"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537313"}]},{"provider":"redhat-vex","source_id":"CVE-2026-94217","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-94217","license":"CC-BY-4.0","published_at":"2026-09-19T23:39:17Z","modified_at":"2026-09-22T20:39:30Z","summary":"keycloak-services: keycloak-services: UMA scope merge across resource owners via resource name collision","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","source":"CVE-2026-94217"},{"type":"Red Hat","score":"Moderate","source":"CVE-2026-94217"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat Single Sign-On 7","cpe":"cpe:/a:redhat:red_hat_single_sign_on:7","status":"not_affected","packages":["keycloak-services"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-94217"},{"vendor":"Red Hat","product":"Red Hat build of Keycloak 26.6.8","cpe":"cpe:/a:redhat:build_keycloak:26.6::el9","status":"fixed","packages":[],"package_count":0,"fixed":[],"advisories":["RHSA-2026:95761"],"provider":"redhat-vex","source":"CVE-2026-94217"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-94217.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-94217"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537313"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-94217"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94217"}]}],"references":[{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:95761"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-94217"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2537313"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-94217.json"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-94217"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94217"}],"sources":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-3484","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3484","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-08T23:00:00Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2026-94217","url":"https://www.cve.org/CVERecord?id=CVE-2026-94217","license":"CC-BY-4.0","modified_at":"2026-11-06T10:26:26.249Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-94217","url":"https://access.redhat.com/security/cve/CVE-2026-94217","license":"CC-BY-4.0","modified_at":"2026-09-22T20:39:30Z","relation":"self"}]}
