github.com/metal3-io/cluster-api-provider-metal3
Affected
- introduced
0, fixed1.11.8(semver)
Fixed versions
1.11.8
Fix
- Fixed version
1.11.8go get github.com/metal3-io/[email protected]
Advisory
Also known as: GO-2026-5615
CAPM3 vulnerable to Cross-Namespace resource access
Summary
CAPM3 is Metal3's Cluster API (CAPI) provider for baremetal provisioning in Kubernetes. Multiple cross-namespace access control vulnerabilities in Cluster API Provider Metal3 allow users with permissions to create or modify CAPM3 resources in one namespace to reference, read, or claim resources belonging to other namespaces.
Patched In
Description
Four related vulnerabilities were identified and fixed:
1. Cross-namespace Secret references in Metal3Machine
Metal3Machine resources accepted userData, metaData, and networkData secret references pointing to arbitrary namespaces. A user could configure a Metal3Machine to reference secrets in namespaces they do not have access to, and the controller would fetch and use those secrets.
2. Cross-namespace BareMetalHost lookups
The host annotation on Metal3Machine could include a namespace/name format, causing the controller to look up BareMetalHost resources in arbitrary namespaces. This allowed a user to claim or associate with BareMetalHosts belonging to other tenants.
3. Incorrect logical operator in ConsumerRef validation
The Metal3LabelSync controller used AND logic (&&) when validating BareMetalHost ConsumerRef Kind and Group, meaning it only rejected a ConsumerRef when both Kind and Group were wrong. If only one was incorrect (e.g., wrong Kind but correct Group), the validation passed, potentially allowing unauthorized resources to associate with a BareMetalHost.
4. Cross-namespace Metal3DataTemplate references
Metal3DataClaim resources could reference Metal3DataTemplate resources in other namespaces. The controller would reconcile using the referenced template regardless of namespace, allowing data leakage across namespace boundaries.
Impact
These vulnerabilities allow cross-namespace resource access within the CAPM3 management cluster. A user with permissions to create or modify Metal3Machine or Metal3DataClaim resources in one namespace could reference secrets, BareMetalHosts, or data templates in other namespaces.
Practical impact is limited because:
Environments with elevated risk:
In the common single-team deployment model, these issues represent a defense-in-depth gap rather than a directly exploitable privilege escalation.
Prerequisites for exploitation
Workarounds
If upgrading is not immediately possible:
Resources
Medium Basis: The source's own band: MODERATE
0, fixed 1.11.8 (semver)1.11.8
1.11.8go get github.com/metal3-io/[email protected]1.12.0, fixed 1.12.5 (semver)1.12.5
1.12.5go get github.com/metal3-io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0