CVE-2026-123047: Eclipse BaSyx Helm Charts · Cleartext Storage of Sensitive Information
Affects Eclipse BaSyx Helm ChartsSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.12.2 soon.
Data as of 5 Nov 2026, 12:34 UTC
Thin evidence
One scorer or none| CNA (eclipse) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 3.12.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade Eclipse BaSyx Helm Charts to 3.12.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse BaSyx Helm Charts | Affected
| Fixed in
|
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.
References
- github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8v (opens in a new tab)
- github.com/eclipse-basyx/charts/pull/106 (opens in a new tab)
- github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2 (opens in a new tab)
- gitlab.eclipse.org/security/cve-assignment/-/work_items/547 (opens in a new tab)