# CVE-2026-105305: Keycloak-services: keycloak-services: device authorization grant bypasses per-client minimum.acr.value enforcement

> Attackers with stolen passwords can bypass mandatory multi-factor authentication in Keycloak's Device Authorization Grant flow to access the Admin REST API.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-ggxp-hq23-v84f

## What is CVE-2026-105305?

CVE-2026-105305 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 6 Oct 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 OIDC implementation of Keycloak, specifically within the Device Authorization Grant flow. This component allows devices with limited input capabilities to obtain security tokens. The issue occurs because the flow fails to check the minimum authentication level required by a client configuration. This allows an attacker who has stolen a user's password to bypass mandatory multi-factor authentication and gain unauthorized access to the Keycloak Admin REST API.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-105305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105305 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 6 Oct 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-105305 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-105305/ (Markdown: https://insights.sbomify.com/CVE-2026-105305/index.md)
```

## Sources

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

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