# CVE-2026-88770: Keycloak-services: keycloak-services: device authorization grant issues tokens to brute-force-locked accounts

> Attackers with active sessions can bypass brute-force account locks in Keycloak to obtain new tokens and maintain unauthorized access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-q4q6-f3mm-hfmv

## What is CVE-2026-88770?

CVE-2026-88770 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-88770?


## How do I fix CVE-2026-88770?

No fix has been published for CVE-2026-88770 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88770 being exploited?

There is no known exploitation of CVE-2026-88770 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88770 and fix it if it is affected.

What it is: CVE-2026-88770 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88770 in the wild and no public exploit code.

Affected product: Red Hat Build of Keycloak. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88770/ (Markdown: https://insights.sbomify.com/CVE-2026-88770/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88770
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88770
- OSV: https://osv.dev/vulnerability/CVE-2026-88770

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88770/
Summaries are generated and may contain mistakes; the official description above is the record.