# CVE-2026-107604: Information disclosure in Red Hat Build of Keycloak

> Realm administrators with view-clients role can retrieve active client secrets, enabling client impersonation and unauthorized service account access.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-ch4r-x5r9-rqr3

## What is CVE-2026-107604?

CVE-2026-107604 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the installation provider and client registration endpoints of the Keycloak identity management service. A realm administrator with only the read-only view-clients role can access the active primary secret of any confidential client, which should normally be restricted. This exposed secret can be used to impersonate the client and gain unauthorized access to its associated service account permissions.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-107604 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107604 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107604 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-107604/ (Markdown: https://insights.sbomify.com/CVE-2026-107604/index.md)
```

## Sources

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

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