EUVD-2026-39475
GHSA-gfv4-4vr2-rr4g
Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
AC:H reflects the multi-condition configuration dependency (PERMISSIVE mode plus ownerManagedAccess plus absent type policy); PR:L confirms authenticated access required; no availability impact applies.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Lifecycle Timeline
1DescriptionCVE.org
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.
AnalysisAI
Authorization bypass in Red Hat Build of Keycloak's UMA engine lets an authenticated user who holds a valid permission ticket for a single resource escalate access to all resources of the same type on the resource server by crafting a specific permission request prefix. The bypass is silently permitted when the resource server operates in PERMISSIVE enforcement mode with ownerManagedAccess enabled and no explicit type-level policy in place. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | All four of the following conditions must hold simultaneously: (1) the attacker is an authenticated user (PR:L) holding at least one legitimate UMA permission ticket for any resource on the target resource server; (2) the resource server is explicitly configured in PERMISSIVE policy enforcement mode - this is not the default hardened setting; (3) the target resource type has ownerManagedAccess enabled, allowing user-delegated access management; (4) no explicit policy exists at the resource type level - only per-resource policies are present, leaving the type unprotected under PERMISSIVE fallback. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 4.6 (Medium) reflects the constrained impact profile: network-reachable (AV:N), low complexity (AC:L), requiring low privileges (PR:L) and user interaction (UI:R), with limited confidentiality and integrity impact only. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An authenticated user who legitimately holds a UMA permission ticket scoped to a single resource (e.g., report:user-42) crafts a permission request using a type-scoped prefix (e.g., report:) that matches all resources of that type on the resource server. Because no explicit type-level policy exists and the server is in PERMISSIVE mode, Keycloak's authorization engine grants the request, allowing the attacker to read or modify all report-type resources belonging to other users within the same resource server. … |
| Remediation | No patched version has been identified in the available data - the CPE wildcard and absence of a fixed-version reference in either the Red Hat advisory (https://access.redhat.com/security/cve/CVE-2026-9799) or Bugzilla entry (https://bugzilla.redhat.com/show_bug.cgi?id=2482471) indicate patch availability should be confirmed directly with Red Hat before upgrading. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Red Hat Build Of Keycloak
View allAuthorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con
Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re
Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus
Identity linking bypass in Red Hat build of Keycloak allows an attacker controlling a second account on the same upstrea
Authenticated users with uma_protection role in Red Hat Keycloak can bypass User-Managed Access policy validation to gai
Privilege escalation in Keycloak (Red Hat Build of Keycloak) lets an authenticated delegated admin with management right
Denial of service in Red Hat build of Keycloak allows remote unauthenticated attackers to exhaust CPU and worker threads
Denial of Service in Red Hat Build of Keycloak allows unauthenticated remote attackers to exhaust server resources by su
Session fixation in Keycloak's login-actions endpoints allows remote attackers to hijack authenticated sessions and take
Authorization code forgery in Red Hat Keycloak enables unauthenticated attackers to escalate privileges to admin-level a
Stored Cross-Site Scripting in Red Hat Build of Keycloak lets an authenticated administrator with `manage-client` permis
Open redirect in Red Hat Build of Keycloak allows authenticated attackers with control over another path on the same web
Same technique Authentication Bypass
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today