CVE-2026-9798

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in Keycloak, an open-source identity and access management solution. When a user account is temporarily locked due to repeated failed login attempts, an attacker with valid client credentials can exploit the Client-Initiated Backchannel Authentication (CIBA) flow to bypass this brute-force protection. This allows continued authentication attempts and token issuance even when the account should be locked, potentially enabling further unauthorized access attempts.

CVSS v3
4.3
EG Score
4.3(medium)
EPSS
10.7%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 3, 2026

Advisory Details (2)

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

2482470 – (CVE-2026-9798) CVE-2026-9798 keycloak: Keycloak: Brute-force protection bypass in CIBA flow

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

cve-details

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

Vendor Advisories for CVE-2026-9798(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
mavenorg.keycloak:keycloak-servicesghsa

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

Frequently asked(5)

What is CVE-2026-9798?
CVE-2026-9798 is a medium vulnerability published on May 28, 2026. A flaw was found in Keycloak, an open-source identity and access management solution. When a user account is temporarily locked due to repeated failed login attempts, an attacker with valid client credentials can exploit the Client-Initiated Backchannel Authentication (CIBA) flow to bypass this…
When was CVE-2026-9798 disclosed?
CVE-2026-9798 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9798 actively exploited?
CVE-2026-9798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9798?
CVE-2026-9798 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-9798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9798, 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-9798

Explore →

Is Your Infrastructure Affected by CVE-2026-9798?

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