Medium, CVSS 6.5GoPublished
Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD
CVE-2025-29781 · GHSA-c98h-7hp9-v9hq
- Affected
- Go github.com/metal3-io/baremetal-operator/apis >= 0.9.0, <= 0.9.0; <= 0.8.0
- Fixed in
- 0.8.10.9.1· Vendor fix available
- Issue
- Impact 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 (BMCES). An adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a BMCES in their authorized namespace and then load Secrets from their unauthorized namespaces to their authorized namespace via the Baremetal Operator controller's cluster scoped privileges, causing Secret leakage. Patches The patch makes BMO refuse to read Secrets from other namespace than where the corresponding Bare Metal Host (BMH) resource is. The patch does not change the BMCEventSubscription API in BMO, but stricter validation will deny the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES resource has already been deployed. The issue exists for all…
Recommended action: Upgrade to 0.9.1 or 0.8.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.