{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123047 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123047 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123047 is a high-severity vulnerability in Eclipse BaSyx Helm Charts, published on 5 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123047 and fix it if it is affected.\n\nWhat it is: CVE-2026-123047 is a high-severity vulnerability in Eclipse BaSyx Helm Charts, published on 5 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123047 in the wild and no public exploit code.\n\nAffected product: Eclipse BaSyx Helm Charts. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-123047/ (Markdown: https://insights.sbomify.com/CVE-2026-123047/index.md)","id":"CVE-2026-123047","markdown":"https://insights.sbomify.com/CVE-2026-123047/index.md","name":"CVE-2026-123047","record":{"aliases":["GHSA-37v5-fgfq-pwwf"],"analysis":null,"analysis_generated_by":null,"assigner":"eclipse","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"In Eclipse BaSyx Helm Charts versions 3.0.0-rc.1 to 3.12.1 of the `basyx` chart, deployments with the bundled Keycloak enabled store the passwords of the Keycloak users that the chart creates in cleartext in a Kubernetes ConfigMap.\n\nThe template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `\u003crelease\u003e-basyx-keycloak-init-config`. By default this includes the bootstrap administrator user. That user holds the `admin` role and has a non-temporary password. 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 password from the ConfigMap and log in to Keycloak as this user. The resulting token carries the `admin` role, which the default BaSyx ABAC rules map to full rights on all BaSyx APIs in the deployment.\n\nThe bundled Keycloak is disabled by default. The issue is fixed in version 3.12.2 of the `basyx` chart, which moves the initialization users to the Keycloak credentials Secret. Affected users should upgrade and change the passwords of users that were created through the chart.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Keycloak admin user password stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts","id":"CVE-2026-123047","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Keycloak admin client secret stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts","id":"CVE-2026-123059"},"nickname":null,"packages":[],"prev":{"headline":"ContentPen \u003c 1.1.1 - Unauthenticated Stored XSS via API Key Disclosure","id":"CVE-2026-123044"},"products":["Eclipse BaSyx Helm Charts"],"published":"2026-11-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-05","vendors":["Eclipse Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123047/"}