# CVE-2026-123047: Keycloak admin user password stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Eclipse Foundation / Eclipse BaSyx Helm Charts: ≥ 3.0.0-rc.1; < 3.12.2 (affected, custom). Source: CNA: eclipse

## Severity and prioritization

- CVSS 3.1: 7.5 (high); CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: eclipse

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-312, CWE-522

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8v (CNA: eclipse)

- https://github.com/eclipse-basyx/charts/pull/106 (CNA: eclipse)

- https://github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2 (CNA: eclipse)

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/547 (CNA: eclipse)

## Provenance

- CNA: eclipse: https://www.cve.org/CVERecord?id=CVE-2026-123047; retrieved 2026-11-05; source updated 2026-11-05

Revision: e7cfdfbda19868deefe90f5eb119f2ccfb18033dce76c6350d1513222f2fe8b8

Canonical: https://y2.dev/cve/CVE-2026-123047

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.