CVE-2026-9792

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-05-28. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in Keycloak's Client Policies, specifically within the org.keycloak.protocol.oidc component. When certain condition providers (client-type, client-roles, client-attributes, client-scopes) are used to enforce security restrictions, the reject-ropc-grant executor is silently bypassed. This allows an unauthenticated remote attacker to obtain tokens via a Resource Owner Password Credentials (ROPC) grant, even when a policy is explicitly configured to block it. This bypass can lead to unauthorized access and information disclosure.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
18.5%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 26, 2026

Advisory Details (4)

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

2482459 – (CVE-2026-9792) CVE-2026-9792 keycloak: Keycloak: Security restriction bypass allows unauthorized ROPC token acquisition

https://bugzilla.redhat.com/show_bug.cgi?id=2482459
redhat Patch Available

cve-details

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.6-62026-06-10redhat

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 9× in last 7d / 63× 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 124 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9792?
CVE-2026-9792 is a medium vulnerability published on May 28, 2026. A flaw was found in Keycloak's Client Policies, specifically within the org.keycloak.protocol.oidc component. When certain condition providers (client-type, client-roles, client-attributes, client-scopes) are used to enforce security restrictions, the reject-ropc-grant executor is silently…
When was CVE-2026-9792 disclosed?
CVE-2026-9792 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9792 actively exploited?
CVE-2026-9792 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9792?
CVE-2026-9792 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-9792?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9792, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9792?

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