CVE-2026-123047
Keycloak admin user password stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-123047 divulgada · CVSS 7.5 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Eclipse BaSyx Helm Charts deployments with the bundled Keycloak enabled store Keycloak user passwords in cleartext in a Kubernetes ConfigMap, so an attacker who can reach the deployment over the network with a low-privilege login can read the bootstrap administrator's password and sign in to Keycloak as that admin. The admin role then grants full rights across all BaSyx APIs in the deployment.
Only affects Eclipse BaSyx Helm Charts basyx chart versions 3.0.0-rc.1 to 3.12.1 with the bundled Keycloak enabled (keycloak.enabled=true). Fixed in 3.12.2.
Descripción original del registro (eclipse)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Eclipse BaSyx Helm Charts |
Corregida | 3.12.2 | — | — |
3.12.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8vhttps://gitlab.eclipse.org/security/cve-assignment/-/work_items/547https://github.com/eclipse-basyx/charts/pull/106https://github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
