{"id":"EM-20261105-1YTB","url":"https://cyber.eventmonitor.net/incident/EM-20261105-1YTB/eclipse-basyx-helm-charts-vulnerability-cve-2026-123059/","type":"cve","title":"Eclipse BaSyx Helm Charts Vulnerability (CVE-2026-123059)","subtitle":"CVE-2026-123059","subject":"CVE-2026-123059","status":"Developing","severity":"high","affected":[],"headline":null,"born":"2026-11-05T14:17:04.940Z","firstSignal":"2026-11-05T13:13:17.000Z","lastSignal":"2026-11-05T14:17:04.940Z","updated":"2026-11-06T12:16:45.734Z","revision":1,"life":[{"status":"Born","at":"2026-11-05T14:17:04.940Z","why":"second independent source: C6 NVD CVE API 2.0"},{"status":"Developing","at":"2026-11-05T14:17:04.940Z","why":"signals keep joining"}],"changeLog":[{"at":"2026-11-05T13:13:17.000Z","what":"First signal: C41 Red Hat Security Data"},{"at":"2026-11-05T14:17:04.940Z","what":"Born: second source, C6 NVD CVE API 2.0. Page EM-20261105-1YTB created."}],"stages":[{"name":"Disclosed","at":"2026-11-05T14:17:04.940Z","detail":"C6 NVD published"},{"name":"Scored","at":"2026-11-05T14:17:04.940Z","detail":"CVSS 7.5"},{"name":"Exploited","at":null,"detail":"No exploitation reported"},{"name":"Advisories","at":null,"detail":"None yet"},{"name":"Vendor Response","at":"2026-11-05T13:13:17.000Z","detail":"C41 published"},{"name":"Resolved","at":null,"detail":"After 14 quiet days"}],"signals":[{"at":"2026-11-05T13:13:17.000Z","source":"C41","sourceName":"Red Hat Security Data","role":"Vendor","severity":3,"title":"Red Hat: CVE-2026-123059 (important)","text":"aas-basyx-v2-full: aas-basyx-v2-full: Privilege escalation via cleartext administrative secret in ConfigMap","url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-123059.json"},{"at":"2026-11-05T14:17:04.940Z","source":"C6","sourceName":"NVD CVE API 2.0","role":"Database","severity":3,"title":"CVE-2026-123059 (CVSS 7.5)","text":"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.\n\n\n\nThe 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…","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-123059"}],"crowd":[],"reference":{"nvd":{"published":"2026-11-05T14:17:04.940","score":7.5,"severity":"HIGH","desc":"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…","product":"","seen":1793930371444},"kev":null,"epss":null,"p0":false},"mergedInto":null,"publisher":"Event Monitor Cyber"}