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 — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 20, 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(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel92026-08-05redhat
redhatrhbk/keycloak-rhel9-operator:26.6-112026-08-05redhat
redhatrhbk/keycloak-rhel9-operator:26.4-222026-08-05redhat
mavenorg.keycloak:keycloak-services—ghsa

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.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.keycloak:keycloak-services26.5.0 ... 26.6.4 (13 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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 211 total refreshes for this CVE.

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

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 August 20, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 71.6% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs