Description
A flaw was found in org.keycloak.authorization. An authenticated user with a granted User-Managed Access (UMA) permission ticket for one resource can exploit this by using a specific permission request prefix to bypass per-resource access control. This allows the user to gain unauthorized access to all resources of that type within the same resource server, even if they do not have a ticket for those specific resources. This vulnerability requires the resource server to be configured in PERMISSIVE policy enforcement mode and affects typed resources with ownerManagedAccess enabled, where no explicit policy protects the resource type. The primary consequence is unauthorized information disclosure or modification of resources.
Affected products
redhat: build of keycloak
References6
- access.redhat.com/errata/RHSA-2026:30049 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:30050 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:30083 Vendor Advisory
- access.redhat.com/errata/RHSA-2026:30084 Vendor Advisory
- access.redhat.com/security/cve/CVE-2026-9799 Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2482471 Vendor Advisory
Metrics
- CVSS 3.1
-
4.6
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 22 · as of 16 November 2026
- CWE
- CWE-639
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.