CVE-2026-123059
Keycloak admin client secret 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-123059 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 (the aas-basyx-v2-full chart with the bundled Keycloak enabled) stores a Keycloak client secret in cleartext in a Kubernetes ConfigMap, so a remote attacker with low privileges can read it. Using the secret, the attacker can obtain an admin-role token that grants full create, read, update, and delete access to all BaSyx repositories and registries in the deployment.
Only affects aas-basyx-v2-full chart 2.2.0 when the bundled Keycloak is enabled (keycloak.enabled=true). No fixed release of the chart exists.
Descripción original del registro (eclipse)
In Eclipse BaSyx Helm Charts version 2.2.0 of the `aas-basyx-v2-full` chart, deployments with the bundled Keycloak enabled store the client secret of the `basyx-technical-user` OAuth2 client in cleartext in a Kubernetes ConfigMap. This client uses the client-credentials grant and its service account holds the realm `admin` role. The chart correctly writes `keycloak.technicalUser.clientSecret` to a Kubernetes Secret, but the template `basyx-keycloak-realm.yaml` also substitutes the same value into the Keycloak realm-import JSON, which is stored in the ConfigMap `<keycloak.fullnameOverride>-realm`. 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 client secret from the ConfigMap. They can then exchange it at the Keycloak token endpoint for an access token with the `admin` role. That token grants full create, read, update, delete and execute rights on all BaSyx repositories and registries in the deployment. The bundled Keycloak is disabled by default. No fixed release of the `aas-basyx-v2-full` chart exists. Affected users should migrate to the `basyx` chart, or deploy without the bundled Keycloak and rotate the `basyx-technical-user` client secret.
Condiciones y alcance
Desglose de métricas
Versiones afectadas
2.2.0Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Eclipse BaSyx Helm Charts |
Sin parche | — | — | — |
Arsenal 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/546https://github.com/eclipse-basyx/charts/pull/46https://github.com/eclipse-basyx/charts/releases/tag/aas-basyx-v2-full-2.2.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
