PoC Monitor
← All CVEs
CVE-2026-123059published 5 Nov 2026 13:13 UTCData: JSON · API

Eclipse Foundation Eclipse BaSyx Helm Charts

Keycloak admin client secret stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-312
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Eclipse Foundation Eclipse BaSyx Helm Charts
  • 2.2.0

Mitigation

No fixed release of the `aas-basyx-v2-full` chart exists. Affected users should migrate to the `basyx` chart.

Workaround

Deploy without the bundled Keycloak and rotate the `basyx-technical-user` client secret.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published5 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.