CVE-2026-4636 is an authorization flaw in Keycloak's User-Managed Access (UMA) handling. An authenticated user holding the uma_protection role can bypass UMA policy validation during policy creation by submitting resource identifiers that belong to other users, even when the request URL path references a resource owned by the attacker. This mismatch between the path-scoped resource context and the resource identifiers accepted in the policy creation request allows cross-user permission grants. As a result, the attacker can create effective permissions over victim-owned resources, obtain a Requesting Party Token (RPT) for those resources, and use that token to access protected data or invoke unauthorized operations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authorization bypass vulnerability in Keycloak where an authenticated user with the uma_protection role can bypass UMA policy validation and gain unauthorized access to victim-owned resources.
A Keycloak UMA policy bypass that allows authenticated users to gain unauthorized access to resources owned by other users.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.