# CVE-2026-117688: Keycloak-services: keycloak-services: vault secret disclosure via client registration installation configuration


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-jjgf-8hh9-873m

## What is CVE-2026-117688?

CVE-2026-117688 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 29 Oct 2026. 

### Official description

A flaw was found in the client registration component of Keycloak, an open-source identity and access management solution. When a vault provider is used to store sensitive information, an authenticated client owner can use a specially crafted reference to trick the system into revealing secrets. By updating a client secret to point to a vault entry and then requesting the client configuration, the owner can see the secret value in plain text. This could lead to the exposure of sensitive credentials that the user should not be able to access.

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

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


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

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

## Is CVE-2026-117688 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117688 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117688 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-117688/ (Markdown: https://insights.sbomify.com/CVE-2026-117688/index.md)
```

## Sources

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

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