Skip to content
VulniPulse
Medium6.5Red Hat Linux

Medium [CVE-2026-88770] Device Authorization Grant issues tokens to brute-force-locked accounts

This medium-severity Red Hat Linux advisory covers CVE-2026-88770 affecting Red Hat Build of Keycloak, Red Hat Single Sign-On 7.

CVE-2026-88770 Published Sep 9, 2026Updated by vendor Sep 9, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to hold a valid SSO browser session for the target account established prior to the lockout.

Successful exploitation allows an attacker to bypass brute-force protection policies and obtain valid tokens for a locked account. The vulnerability's root cause is the missing brute-force status check in the Device Authorization Grant token redemption code path.

Weakness: CWE-307. Affected Red Hat products: Red Hat Build of Keycloak; Red Hat Single Sign-On 7.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 54 minutes ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 54 minutes ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Official advisory · high-confidence parse· fetched 54 minutes ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.