CVE-2026-123047 · Infrastructure
NO FIX YET · SEE WHAT TO DO
The basyx Helm chart writes Keycloak initialization users, including their passwords, into a Kubernetes ConfigMap instead of a Secret when the bundled Keycloak is enabled. A principal with ConfigMap read access in the release namespace, such as the built-in Kubernetes view role, can read the bootstrap admin password and log in as an admin with full BaSyx API rights.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running the Eclipse BaSyx Helm chart with the bundled Keycloak enabled, which is off by default. Exposure comes from the ConfigMap holding plaintext passwords, so any principal with ConfigMap read access in that namespace, including the Kubernetes view role, can read them. Deployments with the bundled Keycloak disabled, or using an external identity provider, are not affected by this specific flaw.
Not affected if chart-3.12.2-or-later, external-identity-provider, keycloak-disabled
Who cares eclipse-basyx, helm, keycloak, kubernetes
basyx release values (keycloak.enabled set to true).<release>-basyx-keycloak-init-config containing a users.json key with credentials values.3.0.0-rc.1 to 3.12.1.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
basyx chart to 3.12.2, which moves initialization users to the Keycloak credentials Secret.This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.