CVE-2026-123059

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

Products / packages Eclipse Foundation Eclipse BaSyx Helm Charts

Published 05/11/2026, 13:13:17 UTC

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 01:50:31 UTC

eclipse · CVSS:3.1 · 7.5

Assessment vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Severity

high7.5

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

Eclipse BaSyx Helm Charts version 2.2.0 stores the Keycloak admin client secret in cleartext in a ConfigMap, accessible to principals with ConfigMap read access. This weakness, CWE-312 and CWE-522, may allow access to an admin role token. The bundled Keycloak is disabled by default.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Eclipse Foundation · eclipse

Eclipse BaSyx Helm Charts

1 range

eclipse version evidence

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

2.2.0

semver versions

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

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

eclipse guidance ↗

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

eclipse guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

4 sources

eclipse-basyx/charts · security/advisories/GHSA-6438-759f-6f8v

Security advisoryeclipse

eclipse-basyx/charts · pull request #46

Patcheclipse

eclipse-basyx/charts · releases/tag/aas-basyx-v2-full-2.2.0

Release noteseclipse

gitlab.eclipse.org/security/cve-assignment/-/work_items/546

Security advisoryeclipse

Inside the record

Evidence available

Package identity · not supplied

Version evidence

Remediation guidance

Weakness classification

Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-123059

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-312 ↗

CWE-312 Cleartext storage of sensitive information

eclipse

CWE-522 ↗

CWE-522 Insufficiently Protected Credentials

eclipse

Contributing organizations · 2

eclipse

Assigning organization

2026-11-05

CISA-ADP

Additional data publisher

2026-11-05

Timeline

All times UTC

5 Nov 2026, 13:13
Advisory published
Publication date supplied by the source.
5 Nov 2026, 21:24
Source updated
Latest modification date supplied by the source.
5 Nov 2026, 23:45
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

CVE · CVE-2026-1230592026-11-05

Observed 2026-11-05T23:45:54.635Z · upstream updated 2026-11-05T21:24:55.109Z

Prioritization updated

before

[]

after

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-05T21:24:06.286598Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.

Reading the signals

Severity · CVSS: Technical impact and attack conditions. The headline is the highest imported catalog score; sources may disagree.
Observed exploitation · KEV: An absent or unavailable KEV listing does not establish that exploitation has not occurred.
Predicted exploitation · EPSS: No EPSS estimate available in this record.

CISA-ADP · SSVC

CISA Coordinator · 2026-11-05

Exploitation: none
Automatable: no
Technical Impact: total

SSVC describes the publisher’s decision context. Your organization’s exposure and priorities may differ.

Record identifiers

Aliases: None recorded

Source evidence

Request a correction or dispute

Start with the assigning organization for this record. Include the CVE ID, the disputed information, and supporting evidence. A dispute does not itself reject a record.

Find the responsible CNA →Official dispute and escalation process ↗

CVE CVE-2026-123059

Enrichment coverage

NVDNo result

Checked 05/11/2026, 13:30:35 UTC

GHSANo result

Checked 05/11/2026, 13:30:35 UTC

EUVDNo result

Checked 05/11/2026, 13:30:36 UTC

EPSSNo result

Checked 05/11/2026, 13:30:35 UTC

Sponsored by MoxsoBuild security habits with adaptive training and phishing simulations.View as JSON

Investigate in your agent.

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

Severity and exploitation

What this means

Attack conditions

Affected versions

Eclipse BaSyx Helm Charts

affected

unaffected

unknown

What to do

Public exploit evidence

Original source description

References

Inside the record

Evidence available

Original records

Underlying weaknesses

Timeline

Advisory published

Source updated

Last imported by cve.new

What changed