# CVE-2026-123059: Keycloak admin client secret stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-86r8-p43m-77rx

## What is CVE-2026-123059?

CVE-2026-123059 is a high-severity vulnerability in Eclipse BaSyx Helm Charts, published on 5 Nov 2026. 

### Official description

In Eclipse BaSyx Helm Charts version 2.2.0 of the `aas-basyx-v2-full` chart, deployments with the bundled Keycloak enabled store the client secret of the `basyx-technical-user` OAuth2 client in cleartext in a Kubernetes ConfigMap. This client uses the client-credentials grant and its service account holds the realm `admin` role.

The chart correctly writes `keycloak.technicalUser.clientSecret` to a Kubernetes Secret, but the template `basyx-keycloak-realm.yaml` also substitutes the same value into the Keycloak realm-import JSON, which is stored in the ConfigMap `<keycloak.fullnameOverride>-realm`. A principal that can read ConfigMaps but not Secrets in the release namespace, such as a holder of the built-in Kubernetes `view` ClusterRole, can read the client secret from the ConfigMap. They can then exchange it at the Keycloak token endpoint for an access token with the `admin` role. That token grants full create, read, update, delete and execute rights on all BaSyx repositories and registries in the deployment.

The bundled Keycloak is disabled by default. No fixed release of the `aas-basyx-v2-full` chart exists. Affected users should migrate to the `basyx` chart, or deploy without the bundled Keycloak and rotate the `basyx-technical-user` client secret.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-123059 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123059 is a high-severity vulnerability in Eclipse BaSyx Helm Charts, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123059 in the wild and no public exploit code.

Affected product: Eclipse BaSyx Helm Charts. 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-123059/ (Markdown: https://insights.sbomify.com/CVE-2026-123059/index.md)
```

## Sources

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

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