Skip to content
Fencer Intel
medium 4.6

CVE-2026-9799 json

Keycloak: keycloak: unauthorized access to resources via uma permission ticket bypass

published 4mo ago modified 13d ago also BIT-keycloak-2026-9799 , EUVD-2026-39475 , GHSA-w3p3-7cjg-vgfw

cvss
4.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.keycloak:keycloak-services 26.6.4
  • bitnami keycloak 26.4.13, 26.6.4
  • Red Hat Red Hat build of Keycloak 26.4 26.4-19, 26.4.13-1
  • Red Hat Red Hat build of Keycloak 26.6 26.6-8, 26.6.4-2

Is CVE-2026-9799 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2026-9799 updated cvss 4.6

keycloak: Keycloak: Unauthorized access to resources via UMA permission ticket bypass

  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-19, rhbk/keycloak-rhel9-operator 26.4-19, rhbk/keycloak-operator-bundle 26.4.13-1
    fixed: vendor fix RHSA-2026:30050
  • Red Hat build of Keycloak 26.4.13
    fixed: vendor fix RHSA-2026:30049
  • Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-8, rhbk/keycloak-rhel9-operator 26.6-8, rhbk/keycloak-operator-bundle 26.6.4-2
    fixed: vendor fix RHSA-2026:30084
  • Red Hat build of Keycloak 26.6.4
    fixed: vendor fix RHSA-2026:30083

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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
GitHub 3.1 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
OSV 3.1 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<26.6.4
26.6.4
bitnami keycloak
>=26.4.0, <26.4.13
>=26.6.0, <26.6.4
26.4.13
26.6.4

Affected products

  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.13
  • Red Hat Red Hat build of Keycloak 26.6
  • Red Hat Red Hat build of Keycloak 26.6.4

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Intel 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.