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.
CVE-2026-9799
Score 4.6 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 4.6; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.6
- EG Score
- 4.6(high)
- EPSS
- 6.2%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
July 1, 2026
Advisory Details (4)
Auto-updated Jun 26, 20262482471 – (CVE-2026-9799) CVE-2026-9799 keycloak: Keycloak: Unauthorized access to resources via UMA permission ticket bypass
https://bugzilla.redhat.com/show_bug.cgi?id=2482471Vendor Advisories for CVE-2026-9799(5)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:30084Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Keycloak 26.6.4 Images Security Update
- RHSA-2026:30083Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Keycloak 26.6.4 Security Update
- GHSA-gfv4-4vr2-rr4gGitHub Security AdvisoriesMedium
A flaw was found in org.keycloak.authorization. An authenticated user with a granted User-Managed...
- RHSA-2026:30050Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Keycloak 26.4.13 Images Security Update
- RHSA-2026:30049Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Keycloak 26.4.13 Security Update
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhbk/keycloak-rhel9 | 2026-06-25 | redhat |
| redhat | rhbk/keycloak-rhel9-operator:26.6-8 | 2026-06-25 | redhat |
| redhat | rhbk/keycloak-rhel9-operator:26.4-19 | 2026-06-25 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 46× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 22:28 UTCEG score recompute
- 2026-07-06 22:28 UTCVendor advisory
- 2026-07-06 22:28 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 22:03 UTCEG score recompute
- 2026-07-05 22:03 UTCVendor advisory
- 2026-07-05 22:03 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-04 21:37 UTCEG score recompute
- 2026-07-04 21:37 UTCVendor advisory
- 2026-07-04 21:37 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:13 UTCEG score recompute
- 2026-07-03 21:13 UTCVendor advisory
- 2026-07-03 21:12 UTCGHSA enrichment
- 2026-07-02 20:48 UTCEG score recompute
- 2026-07-02 20:48 UTCVendor advisory
- 2026-07-02 20:48 UTCGHSA enrichment
- 2026-07-02 17:02 UTCEPSS rescore
- 2026-07-01 20:23 UTCEG score recompute
- 2026-07-01 20:23 UTCVendor advisory
- 2026-07-01 20:23 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
Show 21 moreShow fewer
- 2026-06-30 19:59 UTCEG score recompute
- 2026-06-30 19:59 UTCVendor advisory
- 2026-06-30 19:58 UTCGHSA enrichment
- 2026-06-29 19:34 UTCEG score recompute
- 2026-06-29 19:34 UTCVendor advisory
- 2026-06-29 19:34 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 19:10 UTCEG score recompute
- 2026-06-28 19:10 UTCVendor advisory
- 2026-06-28 19:10 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 18:45 UTCEG score recompute
- 2026-06-27 18:45 UTCVendor advisory
- 2026-06-27 18:45 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 18:20 UTCEG score recompute
- 2026-06-26 18:20 UTCVendor advisory
- 2026-06-26 18:20 UTCGHSA enrichment
- 2026-06-25 17:50 UTCEG score recompute
- 2026-06-25 17:48 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-9799?
When was CVE-2026-9799 disclosed?
Is CVE-2026-9799 actively exploited?
What is the CVSS score of CVE-2026-9799?
How do I remediate CVE-2026-9799?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9799
Is Your Infrastructure Affected by CVE-2026-9799?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.