Keycloak code execution via UMA policy abuse

published 2020-05-08 6 y ago modified 2026-06-17 4 mo ago also GHSA-9c24-43p5-fv82 , EUVD-2022-3346

cvss: 6.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits: 0; none known

A flaw was found in Keycloak’s user-managed access interface, where it would permit a script to be set in the UMA policy. This flaw allows an authenticated attacker with UMA permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the user running application.

Patch / fix

fixed in 2

maven org.keycloak:keycloak-authz-client 8.0.0
redhat keycloak 8.0.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-10169 updated 2025-11-21 cvss 6.6

keycloak: script execution via UMA policy trigger

Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
affected: no fix available
Red Hat Single Sign-On 7.3.4 zip
fixed: vendor fix RHSA-2019:3050

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.28% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.6	CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.keycloak:keycloak-authz-client	<8.0.0	8.0.0

Affected products

[UNKNOWN] keycloak

Classification

Weakness

CWE-267 Privilege Defined With Unsafe Actions

References

bugzilla.redhat.com /show_bug.cgi?id=CVE-2019-10169
web, issue-tracking, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2019-10169
advisory
github.com /keycloak/keycloak
package
security.snyk.io /vuln/SNYK-JAVA-ORGKEYCLOAK-568797
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary