Skip to main content
VulnerabilityPublished

CVE-2026-123059: Eclipse BaSyx Helm Charts · Cleartext Storage of Sensitive Information

Affects Eclipse BaSyx Helm ChartsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 5 Nov 2026, 13:19 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 3.17.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse BaSyx Helm ChartsAffected
  • =2.2.0
Fixed in–

AI-suggested

No fixed release of the affected 'aas-basyx-v2-full' chart version 2.2.0 exists. Users should migrate to the 'basyx' chart or deploy without the bundled Keycloak. Additionally, rotating the 'basyx-technical-user' client secret is recommended to prevent unauthorized access. Since the bundled Keycloak is disabled by default, disabling it if not needed reduces exposure.

Description

Eclipse BaSyx Helm Charts version 2.2.0 with the bundled Keycloak enabled stores the client secret of the 'basyx-technical-user' OAuth2 client in cleartext within a Kubernetes ConfigMap. This secret is accessible to principals with read access to ConfigMaps, such as those with the Kubernetes 'view' ClusterRole, allowing them to obtain an admin-level access token. The bundled Keycloak is disabled by default, and no fixed release of the affected chart version exists. Users are advised to migrate to the 'basyx' chart or deploy without the bundled Keycloak and rotate the client secret.

References

Community reviews

Loading reviews…