# CVE-2026-109082: Keycloak-services: keycloak-services: ciba confidential-only contract not enforced for public clients

> Attackers can bypass CIBA security checks to trick users into approving logins, gaining full account access without a client secret.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-68jh-rrf2-v9vr

## What is CVE-2026-109082?

CVE-2026-109082 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the Client-Initiated Backchannel Authentication CIBA implementation within the keycloak-services component of Keycloak. This component handles advanced authentication flows where a client initiates a login on behalf of a user. The issue occurs because Keycloak fails to verify that a client is authorized to use the CIBA flow, allowing public clients to bypass security requirements. An attacker could use this flaw to trick a user into approving a login request, eventually gaining full access to the users account without needing a client secret.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-109082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109082 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-109082 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-109082/ (Markdown: https://insights.sbomify.com/CVE-2026-109082/index.md)
```

## Sources

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

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