CVE-2025-29781 SUSE CVE security@suse.de SUSE Security Team SUSE CVE-2025-29781 Interim 1 4 2026-03-05T01:10:31Z current 2025-03-20T00:12:01Z 2026-03-05T01:10:31Z cve-database/bin/generate-cvrf-cve.pl 2020-12-27T01:00:00Z CVE-2025-29781 The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription`. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. As a workaround, the operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). https://www.suse.com/support/security/rating/ SUSE Security Ratings Image SLE-Micro Image SLE-Micro-Azure Image SLE-Micro-BYOS Image SLE-Micro-BYOS-Azure Image SLE-Micro-BYOS-EC2 Image SLE-Micro-EC2 SUSE Linux Enterprise Server 16.0 openSUSE Tumbleweed cloud-init-25.1.3-slfo.1.1_1.1 cloud-init-config-suse-25.1.3-slfo.1.1_1.1 govulncheck-vulndb-0.0.20250318T181448-1.1 govulncheck-vulndb-0.0.20250814T182633-160000.1.2 cloud-init-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro cloud-init-config-suse-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro cloud-init-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-Azure cloud-init-config-suse-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-Azure cloud-init-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-BYOS cloud-init-config-suse-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-BYOS cloud-init-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-BYOS-Azure cloud-init-config-suse-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-BYOS-Azure cloud-init-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-BYOS-EC2 cloud-init-config-suse-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-BYOS-EC2 cloud-init-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-EC2 cloud-init-config-suse-25.1.3-slfo.1.1_1.1 as a component of Image SLE-Micro-EC2 govulncheck-vulndb-0.0.20250814T182633-160000.1.2 as a component of SUSE Linux Enterprise Server 16.0 govulncheck-vulndb-0.0.20250318T181448-1.1 as a component of openSUSE Tumbleweed The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription`. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. As a workaround, the operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace. CVE-2025-29781 Image SLE-Micro:cloud-init-25.1.3-slfo.1.1_1.1 Image SLE-Micro:cloud-init-config-suse-25.1.3-slfo.1.1_1.1 Image SLE-Micro-Azure:cloud-init-25.1.3-slfo.1.1_1.1 Image SLE-Micro-Azure:cloud-init-config-suse-25.1.3-slfo.1.1_1.1 Image SLE-Micro-BYOS:cloud-init-25.1.3-slfo.1.1_1.1 Image SLE-Micro-BYOS:cloud-init-config-suse-25.1.3-slfo.1.1_1.1 Image SLE-Micro-BYOS-Azure:cloud-init-25.1.3-slfo.1.1_1.1 Image SLE-Micro-BYOS-Azure:cloud-init-config-suse-25.1.3-slfo.1.1_1.1 Image SLE-Micro-BYOS-EC2:cloud-init-25.1.3-slfo.1.1_1.1 Image SLE-Micro-BYOS-EC2:cloud-init-config-suse-25.1.3-slfo.1.1_1.1 Image SLE-Micro-EC2:cloud-init-25.1.3-slfo.1.1_1.1 Image SLE-Micro-EC2:cloud-init-config-suse-25.1.3-slfo.1.1_1.1 SUSE Linux Enterprise Server 16.0:govulncheck-vulndb-0.0.20250814T182633-160000.1.2 openSUSE Tumbleweed:govulncheck-vulndb-0.0.20250318T181448-1.1 moderate