CVE-2026-4636 | Keycloak: keycloak: uma policy bypass allows authenticated users to gain unauthorized access to victim-owned resources.

Exp

A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource identifiers owned by other users in a policy creation request, even if the URL path specifies an attacker-owned resource. Consequently, the attacker gains unauthorized permissions to victim-owned resources, enabling them to obtain a Requesting Party Token (RPT) and access sensitive information or perform unauthorized actions.

Published: 2026-04-02 Last update: 2026-04-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-4636 is rated Exploit Available (56.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.34%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-4636

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-4636

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.34% +0.31%
2 2026-04-03 — 0.03% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4636

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 5.2 [email protected]

Weakness enumeration for CVE-2026-4636

GitHub Security Advisory for CVE-2026-4636

GHSA-f2hx-5fx3-hmcv · Severity: high · Ecosystem: maven — Keycloak: UMA Policy Resource Injection Allows Unauthorized Cross-User Permission Grants

OS Trackers for CVE-2026-4636

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2026-4636

Affected software / configurations for CVE-2026-4636

Vendor Product Version Raw CPE
redhat build_of_keycloak — cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:text-only:*:*:*
redhat build_of_keycloak 26.2 cpe:2.3:a:redhat:build_of_keycloak:26.2:*:*:*:text-only:*:*:*
redhat build_of_keycloak 26.2.15 cpe:2.3:a:redhat:build_of_keycloak:26.2.15:*:*:*:text-only:*:*:*
redhat build_of_keycloak 26.4 cpe:2.3:a:redhat:build_of_keycloak:26.4:*:*:*:text-only:*:*:*
redhat build_of_keycloak 26.4.11 cpe:2.3:a:redhat:build_of_keycloak:26.4.11:*:*:*:text-only:*:*:*

References for CVE-2026-4636

cvelogic Threat Intelligence