# CVE-2026-82968: Auth bypass in Red Hat Build of Keycloak

> Attackers can hijack user accounts by intercepting social identity linking, allowing unauthorized access to victim profiles in Keycloak.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-2w6p-j7xq-6p7v

## What is CVE-2026-82968?

CVE-2026-82968 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 2 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the first-broker-login flow of the Keycloak identity management service. When a user links a social identity provider account to their local account, the verification proof generated is not strictly bound to the specific upstream identity being verified. This allows an attacker with a different account on the same social provider to intercept the process and link their own account to the victim's local profile, gaining unauthorized access.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-82968 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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