CVE-2026-9799

MEDIUMPre-NVD 4.64.6—
EchelonGraph scoreMEDIUM confidence

Score 4.6 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 4.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity46% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

Published

June 25, 2026

Last Modified

July 1, 2026

Advisory Details (4)

Auto-updated Jun 26, 2026
Patch available. Sources: redhat.
redhat

2482471 – (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=2482471
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-9799

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.6-82026-06-25redhat
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat

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 7× in last 7d / 39× 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.

Showing the most recent 100 of 235 total refreshes for this CVE.

  1. 2026-10-04 23:23 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:57 UTCEPSS rescore
  4. 2026-10-01 19:51 UTCEPSS rescore
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-29 15:24 UTCEPSS rescore
  7. 2026-09-28 13:52 UTCEPSS rescore
  8. 2026-09-27 13:49 UTCEPSS rescore
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-24 14:04 UTCEPSS rescore
  11. 2026-09-23 17:54 UTCEPSS rescore
  12. 2026-09-23 08:44 UTCEG score recompute
  13. 2026-09-23 08:44 UTCVendor advisory
  14. 2026-09-23 08:44 UTCGHSA enrichment
  15. 2026-09-22 16:01 UTCEPSS rescore
  16. 2026-09-21 21:09 UTCEPSS rescore
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 07:22 UTCEG score recompute
  20. 2026-09-18 07:22 UTCVendor advisory
  21. 2026-09-18 07:22 UTCGHSA enrichment
  22. 2026-09-17 19:32 UTCEPSS rescore
  23. 2026-09-16 14:09 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 75 more
  1. 2026-09-14 01:18 UTCEG score recompute
  2. 2026-09-14 01:18 UTCVendor advisory
  3. 2026-09-14 01:18 UTCGHSA enrichment
  4. 2026-09-13 16:48 UTCEPSS rescore
  5. 2026-09-12 15:46 UTCEG score recompute
  6. 2026-09-12 15:46 UTCVendor advisory
  7. 2026-09-12 15:46 UTCGHSA enrichment
  8. 2026-09-12 15:02 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:38 UTCEPSS rescore
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-30 19:32 UTCEG score recompute
  20. 2026-08-30 19:32 UTCVendor advisory
  21. 2026-08-30 19:32 UTCGHSA enrichment
  22. 2026-08-30 19:18 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:42 UTCEPSS rescore
  25. 2026-08-27 23:20 UTCEG score recompute
  26. 2026-08-27 23:20 UTCVendor advisory
  27. 2026-08-27 23:20 UTCGHSA enrichment
  28. 2026-08-27 14:25 UTCEPSS rescore
  29. 2026-08-26 14:47 UTCEPSS rescore
  30. 2026-08-25 13:49 UTCEPSS rescore
  31. 2026-08-24 14:18 UTCEPSS rescore
  32. 2026-08-24 13:09 UTCEG score recompute
  33. 2026-08-24 13:09 UTCVendor advisory
  34. 2026-08-24 13:09 UTCGHSA enrichment
  35. 2026-08-23 10:51 UTCVendor advisory
  36. 2026-08-23 10:50 UTCGHSA enrichment
  37. 2026-08-22 10:25 UTCEG score recompute
  38. 2026-08-22 10:25 UTCVendor advisory
  39. 2026-08-22 10:25 UTCGHSA enrichment
  40. 2026-08-21 23:49 UTCEPSS rescore
  41. 2026-08-21 07:27 UTCEG score recompute
  42. 2026-08-21 07:27 UTCVendor advisory
  43. 2026-08-21 07:27 UTCGHSA enrichment
  44. 2026-08-20 22:56 UTCEPSS rescore
  45. 2026-08-20 07:03 UTCEG score recompute
  46. 2026-08-20 07:03 UTCVendor advisory
  47. 2026-08-20 07:03 UTCGHSA enrichment
  48. 2026-08-19 17:04 UTCEPSS rescore
  49. 2026-08-19 01:23 UTCEG score recompute
  50. 2026-08-19 01:23 UTCVendor advisory
  51. 2026-08-19 01:23 UTCGHSA enrichment
  52. 2026-08-18 13:49 UTCEPSS rescore
  53. 2026-08-17 13:47 UTCEPSS rescore
  54. 2026-08-17 13:18 UTCEG score recompute
  55. 2026-08-17 13:18 UTCVendor advisory
  56. 2026-08-17 13:18 UTCGHSA enrichment
  57. 2026-08-16 14:56 UTCEPSS rescore
  58. 2026-08-16 12:54 UTCEG score recompute
  59. 2026-08-16 12:54 UTCVendor advisory
  60. 2026-08-16 12:54 UTCGHSA enrichment
  61. 2026-08-16 02:15 UTCEPSS rescore
  62. 2026-08-15 12:30 UTCEG score recompute
  63. 2026-08-15 12:30 UTCVendor advisory
  64. 2026-08-15 12:30 UTCGHSA enrichment
  65. 2026-08-15 01:31 UTCEPSS rescore
  66. 2026-08-14 12:05 UTCEG score recompute
  67. 2026-08-14 12:05 UTCVendor advisory
  68. 2026-08-14 12:05 UTCGHSA enrichment
  69. 2026-08-13 22:00 UTCEPSS rescore
  70. 2026-08-13 11:41 UTCEG score recompute
  71. 2026-08-13 11:41 UTCVendor advisory
  72. 2026-08-13 11:41 UTCGHSA enrichment
  73. 2026-08-12 13:51 UTCEPSS rescore
  74. 2026-08-12 11:17 UTCEG score recompute
  75. 2026-08-12 11:17 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-9799?
CVE-2026-9799 is a medium vulnerability published on June 25, 2026. 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…
When was CVE-2026-9799 disclosed?
CVE-2026-9799 was first published on June 25, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9799 actively exploited?
CVE-2026-9799 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9799?
CVE-2026-9799 has a CVSS base score of 4.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9799?
A fix for CVE-2026-9799 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9799 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9799

Explore →

Is Your Infrastructure Affected by CVE-2026-9799?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.