CVE-2026-123059

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

  • High 7.5

Description

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.

Key facts

Published
5 Nov 2026
Last changed
5 Nov 2026
Assigned by
eclipse
EPSS
0.21% likely to be exploited in the next 30 days, higher than 11.25% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (eclipse)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

What to do

  • No fixed release of the `aas-basyx-v2-full` chart exists. Affected users should migrate to the `basyx` chart.CNA solution statement
  • Deploy without the bundled Keycloak and rotate the `basyx-technical-user` client secret.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-37 Retrieve Embedded Sensitive Data (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Eclipse FoundationEclipse BaSyx Helm Charts
  • Default status: unaffected
  • 2.2.0 (affected)

Timeline

  1. 5 Nov 2026 Published

Weakness

References