{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-123047", "assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c", "state": "PUBLISHED", "assignerShortName": "eclipse", "dateReserved": "2026-11-05T08:44:14.855Z", "datePublished": "2026-11-05T12:11:12.591Z", "dateUpdated": "2026-11-05T19:03:36.145Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c", "shortName": "eclipse", "dateUpdated": "2026-11-05T12:11:12.591Z"}, "title": "Keycloak admin user password stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts", "datePublic": "2026-11-05T11:26:00.000Z", "problemTypes": [{"descriptions": [{"lang": "en", "cweId": "CWE-312", "description": "CWE-312 Cleartext storage of sensitive information", "type": "CWE"}]}, {"descriptions": [{"lang": "en", "cweId": "CWE-522", "description": "CWE-522 Insufficiently Protected Credentials", "type": "CWE"}]}], "impacts": [{"capecId": "CAPEC-37", "descriptions": [{"lang": "en", "value": "CAPEC-37 Retrieve Embedded Sensitive Data"}]}], "affected": [{"vendor": "Eclipse Foundation", "product": "Eclipse BaSyx Helm Charts", "versions": [{"status": "affected", "version": "3.0.0-rc.1", "lessThan": "3.12.2", "versionType": "custom"}], "defaultStatus": "unaffected"}], "descriptions": [{"lang": "en", "value": "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\n\n\nThe template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `<release>-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\n\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.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<p>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.</p><p>The template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `&lt;release&gt;-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.</p><p>The 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.</p>"}]}], "references": [{"url": "https://github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8v"}, {"url": "https://github.com/eclipse-basyx/charts/pull/106"}, {"url": "https://github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2"}, {"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/547"}], "metrics": [{"format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}], "cvssV3_1": {"version": "3.1", "attackVector": "NETWORK", "attackComplexity": "HIGH", "privilegesRequired": "LOW", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "availabilityImpact": "HIGH", "baseSeverity": "HIGH", "baseScore": 7.5, "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"}}], "configurations": [{"lang": "en", "value": "Only deployments using the chart\u2019s bundled Keycloak are affected. The vulnerability requires keycloak.enabled=true.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "Only deployments using the chart\u2019s bundled Keycloak are affected. The vulnerability requires <code>keycloak.enabled=true</code>."}]}], "credits": [{"lang": "en", "value": "Eclipse Foundation Security Team", "type": "finder"}], "source": {"discovery": "UNKNOWN"}, "x_generator": {"engine": "Vulnogram 1.0.5"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-11-05T16:54:46.133265Z", "id": "CVE-2026-123047", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-11-05T19:03:36.145Z"}}]}}

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-123047", "assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c", "state": "PUBLISHED", "assignerShortName": "eclipse", "dateReserved": "2026-11-05T08:44:14.855Z", "datePublished": "2026-11-05T12:11:12.591Z", "dateUpdated": "2026-11-05T19:03:36.145Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c", "shortName": "eclipse", "dateUpdated": "2026-11-05T12:11:12.591Z"}, "title": "Keycloak admin user password stored in cleartext in a ConfigMap in Eclipse BaSyx Helm Charts", "datePublic": "2026-11-05T11:26:00.000Z", "problemTypes": [{"descriptions": [{"lang": "en", "cweId": "CWE-312", "description": "CWE-312 Cleartext storage of sensitive information", "type": "CWE"}]}, {"descriptions": [{"lang": "en", "cweId": "CWE-522", "description": "CWE-522 Insufficiently Protected Credentials", "type": "CWE"}]}], "impacts": [{"capecId": "CAPEC-37", "descriptions": [{"lang": "en", "value": "CAPEC-37 Retrieve Embedded Sensitive Data"}]}], "affected": [{"vendor": "Eclipse Foundation", "product": "Eclipse BaSyx Helm Charts", "versions": [{"status": "affected", "version": "3.0.0-rc.1", "lessThan": "3.12.2", "versionType": "custom"}], "defaultStatus": "unaffected"}], "descriptions": [{"lang": "en", "value": "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\n\n\nThe template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `<release>-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\n\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.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<p>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.</p><p>The template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `&lt;release&gt;-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.</p><p>The 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.</p>"}]}], "references": [{"url": "https://github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8v"}, {"url": "https://github.com/eclipse-basyx/charts/pull/106"}, {"url": "https://github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2"}, {"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/547"}], "metrics": [{"format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}], "cvssV3_1": {"version": "3.1", "attackVector": "NETWORK", "attackComplexity": "HIGH", "privilegesRequired": "LOW", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "availabilityImpact": "HIGH", "baseSeverity": "HIGH", "baseScore": 7.5, "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"}}], "configurations": [{"lang": "en", "value": "Only deployments using the chart\u2019s bundled Keycloak are affected. The vulnerability requires keycloak.enabled=true.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "Only deployments using the chart\u2019s bundled Keycloak are affected. The vulnerability requires <code>keycloak.enabled=true</code>."}]}], "credits": [{"lang": "en", "value": "Eclipse Foundation Security Team", "type": "finder"}], "source": {"discovery": "UNKNOWN"}, "x_generator": {"engine": "Vulnogram 1.0.5"}}, "adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-123047", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-11-05T16:54:46.133265Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-11-05T19:03:28.561Z"}}]}}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Eclipse BaSyx Helm Charts", "vendor": "Eclipse Foundation", "versions": [{"lessThan": "3.12.2", "status": "affected", "version": "3.0.0-rc.1", "versionType": "custom"}]}], "source": "emo@eclipse.org"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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\n\n\nThe template `keycloak-init-config.yaml` rendered `keycloak.initialization.users`, including each user's `credentials[].value`, as `users.json` into the persistent ConfigMap `<release>-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\n\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."}], "id": "CVE-2026-123047", "lastModified": "2026-11-05T19:17:17.360", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.6, "impactScore": 5.9, "source": "emo@eclipse.org", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-123047", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-11-05T16:54:46.133265Z", "version": "2.0.3"}}]}, "published": "2026-11-05T13:17:07.493", "references": [{"source": "emo@eclipse.org", "url": "https://github.com/eclipse-basyx/charts/pull/106"}, {"source": "emo@eclipse.org", "url": "https://github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2"}, {"source": "emo@eclipse.org", "url": "https://github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8v"}, {"source": "emo@eclipse.org", "url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/547"}], "sourceIdentifier": "emo@eclipse.org", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-312"}, {"lang": "en", "value": "CWE-522"}], "source": "emo@eclipse.org", "type": "Secondary"}]}

{"bugzilla": {"description": "basyx: Eclipse BaSyx Helm Chart: Privilege escalation via plaintext credential storage in ConfigMap", "id": "2567553", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2567553"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.5", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "status": "draft"}, "cwe": "CWE-260", "details": ["A flaw was found in the Eclipse BaSyx Helm chart. When the bundled Keycloak identity service is enabled, initialization user credentials\u2014including the bootstrap administrator password\u2014are stored in plaintext within a Kubernetes ConfigMap instead of a protected Secret. A user or service account with read access to ConfigMaps within the release namespace can retrieve these credentials and authenticate as an administrator. This allows the attacker to achieve privilege escalation and gain full administrative control over all deployed APIs."], "mitigation": {"lang": "en:us", "value": "Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability."}, "name": "CVE-2026-123047", "public_date": "2026-11-05T12:11:12Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-123047\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-123047\nhttps://github.com/eclipse-basyx/charts/pull/106\nhttps://github.com/eclipse-basyx/charts/releases/tag/basyx-3.12.2\nhttps://github.com/eclipse-basyx/charts/security/advisories/GHSA-6438-759f-6f8v\nhttps://gitlab.eclipse.org/security/cve-assignment/-/work_items/547"], "statement": "Red Hat rates this vulnerability as having an Important impact because exposure of administrative authentication credentials allows users with low-level read permissions to escalate privileges and gain full administrative authority over the deployment. This flaw resides specifically within the packaging templates of the third-party Eclipse BaSyx Helm chart rather than Keycloak itself. No supported Red Hat products package or distribute the affected chart, meaning standard Red Hat environments are not directly exposed.", "threat_severity": "Important"}

{"created": "2026-11-05T13:30:11.679413+00:00", "updated": "2026-11-06T14:30:06.080000+00:00", "vendors": []}