# CVE-2026-123047: Keycloak admin user password 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-37v5-fgfq-pwwf

## What is CVE-2026-123047?

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

### Official description

In Eclipse BaSyx Helm Charts versions 3.0.0-rc.1 to 3.12.1 of the `basyx` chart, deployments with the bundled Keycloak enabled store the passwords of the Keycloak users that the chart creates in cleartext in a Kubernetes ConfigMap.

The template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `<release>-basyx-keycloak-init-config`. By default this includes the bootstrap administrator user. That user holds the `admin` role and has a non-temporary password. 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 password from the ConfigMap and log in to Keycloak as this user. The resulting token carries the `admin` role, which the default BaSyx ABAC rules map to full rights on all BaSyx APIs in the deployment.

The bundled Keycloak is disabled by default. The issue is fixed in version 3.12.2 of the `basyx` chart, which moves the initialization users to the Keycloak credentials Secret. Affected users should upgrade and change the passwords of users that were created through the chart.

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

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


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

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

## Is CVE-2026-123047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123047 is a high-severity vulnerability in Eclipse BaSyx Helm Charts, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123047 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-123047/ (Markdown: https://insights.sbomify.com/CVE-2026-123047/index.md)
```

## Sources

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

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