CVE-2026-88770

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-10. 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.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

A flaw was found in the Device Authorization Grant flow of Keycloak, an identity and access management solution. The issue occurs because the token redemption process fails to check if a user account is currently locked due to brute-force protection. If an attacker has an active session for a locked account, they can complete the device login process and receive new security tokens. This allows the attacker to maintain access to the account even when it should be temporarily disabled to prevent unauthorized entry.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 10, 2026
Patch available. Sources: redhat.
redhat

2531302 – (CVE-2026-88770) CVE-2026-88770 keycloak-services: keycloak-services: Device Authorization Grant issues tokens to brute-force-locked accounts

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

CVE-2026-88770 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

Vendor Advisories for CVE-2026-88770(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 35× 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.

  1. 2026-09-19 02:49 UTCEG score recompute
  2. 2026-09-19 02:49 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 04:10 UTCEG score recompute
  5. 2026-09-18 04:10 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 05:30 UTCEG score recompute
  8. 2026-09-17 05:30 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 06:50 UTCEG score recompute
  11. 2026-09-16 06:50 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 08:12 UTCEG score recompute
  14. 2026-09-15 08:12 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-14 09:33 UTCEG score recompute
  17. 2026-09-14 09:33 UTCGHSA enrichment
  18. 2026-09-13 16:48 UTCEPSS rescore
  19. 2026-09-13 10:54 UTCEG score recompute
  20. 2026-09-13 10:54 UTCGHSA enrichment
  21. 2026-09-12 15:02 UTCEPSS rescore
  22. 2026-09-12 12:15 UTCEG score recompute
  23. 2026-09-12 12:15 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 10 more
  1. 2026-09-11 13:36 UTCEG score recompute
  2. 2026-09-11 13:36 UTCGHSA enrichment
  3. 2026-09-10 14:57 UTCGHSA enrichment
  4. 2026-09-10 11:21 UTCEG score recompute
  5. 2026-09-10 11:20 UTCGHSA enrichment
  6. 2026-09-10 10:56 UTCEG score recompute
  7. 2026-09-10 10:56 UTCGHSA enrichment
  8. 2026-09-10 08:37 UTCEG score recompute
  9. 2026-09-10 07:26 UTCEG score recompute
  10. 2026-09-10 07:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88770?
CVE-2026-88770 is a medium vulnerability published on September 10, 2026. A flaw was found in the Device Authorization Grant flow of Keycloak, an identity and access management solution. The issue occurs because the token redemption process fails to check if a user account is currently locked due to brute-force protection. If an attacker has an active session for a…
When was CVE-2026-88770 disclosed?
CVE-2026-88770 was first published in the National Vulnerability Database on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88770 actively exploited?
CVE-2026-88770 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 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-88770?
CVE-2026-88770 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-88770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88770, 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-88770

Explore →

Is Your Infrastructure Affected by CVE-2026-88770?

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