A flaw was found in the Device Authorization Grant flow of Keycloak, an identity and access management solution. (CVE-2026-88770)
A vulnerability in the Device Authorization Grant flow of Keycloak allows attackers with an active session on a locked user account to bypass brute-force protection and obtain new security tokens. This flaw occurs because the token redemption process does not verify if the user account is currently locked. Exploitation requires the attacker to have a valid single sign-on (SSO) session established before the account lockout. The issue is rated as moderate severity with a CVSS score of 6.5. No official patch or mitigation meeting Red Hat's criteria is currently available.
AI Analysis
Technical Summary
CVE-2026-88770 is a vulnerability in Keycloak's Device Authorization Grant flow where the token redemption process fails to check if a user account is locked due to brute-force protection. An attacker holding an active session for a locked account can complete the device login process and receive new security tokens, effectively bypassing brute-force lockout mechanisms. The root cause is the missing brute-force status check in the token redemption code path. Red Hat has assessed this vulnerability as moderate severity (CVSS 6.5) and notes that exploitation requires a valid SSO session established prior to the account lockout. Currently, no mitigation or patch meeting Red Hat's standards for ease of use, applicability, or stability is available.
Potential Impact
An attacker with a valid active session on a locked user account can bypass brute-force protection policies and obtain valid security tokens, maintaining unauthorized access even when the account should be temporarily disabled. The vulnerability impacts confidentiality by allowing unauthorized token issuance but does not affect integrity or availability. Exploitation requires prior access to an active session, limiting the attack scope.
Mitigation Recommendations
Red Hat states that no mitigation or patch meeting their criteria for ease of use, widespread applicability, or stability is currently available. Users should monitor Red Hat advisories for future updates. Since exploitation requires an active session established before lockout, limiting session lifetimes and monitoring for unusual session activity may help reduce risk, but no official mitigation is provided.
A flaw was found in the Device Authorization Grant flow of Keycloak, an identity and access management solution. (CVE-2026-88770)
Description
A vulnerability in the Device Authorization Grant flow of Keycloak allows attackers with an active session on a locked user account to bypass brute-force protection and obtain new security tokens. This flaw occurs because the token redemption process does not verify if the user account is currently locked. Exploitation requires the attacker to have a valid single sign-on (SSO) session established before the account lockout. The issue is rated as moderate severity with a CVSS score of 6.5. No official patch or mitigation meeting Red Hat's criteria is currently available.
CVSS v3.1
Score 6.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-88770 is a vulnerability in Keycloak's Device Authorization Grant flow where the token redemption process fails to check if a user account is locked due to brute-force protection. An attacker holding an active session for a locked account can complete the device login process and receive new security tokens, effectively bypassing brute-force lockout mechanisms. The root cause is the missing brute-force status check in the token redemption code path. Red Hat has assessed this vulnerability as moderate severity (CVSS 6.5) and notes that exploitation requires a valid SSO session established prior to the account lockout. Currently, no mitigation or patch meeting Red Hat's standards for ease of use, applicability, or stability is available.
Potential Impact
An attacker with a valid active session on a locked user account can bypass brute-force protection policies and obtain valid security tokens, maintaining unauthorized access even when the account should be temporarily disabled. The vulnerability impacts confidentiality by allowing unauthorized token issuance but does not affect integrity or availability. Exploitation requires prior access to an active session, limiting the attack scope.
Mitigation Recommendations
Red Hat states that no mitigation or patch meeting their criteria for ease of use, widespread applicability, or stability is currently available. Users should monitor Red Hat advisories for future updates. Since exploitation requires an active session established before lockout, limiting session lifetimes and monitoring for unusual session activity may help reduce risk, but no official mitigation is provided.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q4q6-f3mm-hfmv
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-88770"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6aa2af5facd9273b4925a61c
Added to database: 09/10/2026, 13:23:43 UTC
Last enriched: 09/10/2026, 13:28:25 UTC
Last updated: 09/11/2026, 03:06:49 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.