GHSA-rf84-wr5g-m3rp: CAPM3 vulnerable to Cross-Namespace resource access
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/metal3-io/cluster-api-provider-metal3 (Go) 1.12.5, 1.11.8.
Low priority for now. Upgrade to github.com/metal3-io/cluster-api-provider-metal3 (Go) 1.12.5, 1.11.8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
## 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 - **v1.13.0** (main branch — all fixes included) - **v1.12.5** (all four fixes backported) - **v1.11.8** (three of four fixes backported; Metal3DataClaim template restriction not applicable due to missing v1beta2 webhook infrastructure) ## 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: - CAPM3 management clusters are typically single-tenant, operated by a single infrastructure/platform team. Namespace boundaries serve as organizational separation (e.g., per workload cluster), not as security isolation between mutually untrusted parties. - Exploiting these issues requires RBAC permissions to create or modify CAPM3 infrastructure resources (Metal3Machine, Metal3DataClaim), which are infrastructure-admin privileges not granted to application developers or end users. - The accessible resources are limited to Metal3 operational artifacts (bootstrap secrets, network metadata, BareMetalHost associations), not arbitrary cluster secrets. Environments with elevated risk: - Management clusters where namespace-scoped RBAC is used to delegate infrastructure provisioning to separate teams with different trust levels. - Managed service providers using a shared management cluster across multiple customer namespaces. 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 - Attacker must have RBAC permissions to create or modify Metal3Machine or Metal3DataClaim resources in at least one namespace. - Target resources (secrets, BareMetalHosts, templates) must exist in other namespaces on the same management cluster. ## Workarounds If upgrading is not immediately possible: 1. Restrict RBAC: Limit who can create/modify Metal3Machine and Metal3DataClaim resources to trusted operators only. 2. Admission policies: Deploy OPA/Gatekeeper or Kyverno policies that reject CAPM3 resources with cross-namespace references. 3. Network policies: While not a direct mitigation, network policies can limit the blast radius of compromised credentials. ## Resources - https://github.com/metal3-io/cluster-api-provider-metal3/pull/3288, https://github.com/metal3-io/cluster-api-provider-metal3/pull/3294 - https://github.com/metal3-io/cluster-api-provider-metal3/pull/3317, https://github.com/metal3-io/cluster-api-provider-metal3/pull/3319, https://github.com/metal3-io/cluster-api-provider-metal3/pull/3323 - https://github.com/metal3-io/cluster-api-provider-metal3/pull/3322, https://github.com/metal3-io/cluster-api-provider-metal3/pull/3325 - https://github.com/metal3-io/cluster-api-provider-metal3/pull/3327, https://github.com/metal3-io/cluster-api-provider-metal3/pull/3343, https://github.com/metal3-io/cluster-api-provider-metal3/pull/3344
- Published
- May 29, 2026
- Updated
- Jun 25, 2026
- EPSS
- —
- CWE
- CWE-863
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/metal3-io/cluster-api-provider-metal3 | pkg:golang/github.com/metal3-io/cluster-api-provider-metal3 |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/metal3-io/cluster-api-provider-metal3 | from 1.12.0 · before 1.12.5 | 1.12.5 |
| Go | github.com/metal3-io/cluster-api-provider-metal3 | before 1.11.8 | 1.11.8 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GO-2026-5615CAPM3 vulnerable to Cross-Namespace resource access in github.com/metal3-io/cluster-api-provider-metal30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/metal3-io/cluster-api-provider-metal3 | 1.11.8 | Package registry (OSV) |
| Go:github.com/metal3-io/cluster-api-provider-metal3 | 1.12.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
- metal3-io/cluster-api-provider-metal3PR 3288
- metal3-io/cluster-api-provider-metal3PR 3294
- metal3-io/cluster-api-provider-metal3PR 3317
- metal3-io/cluster-api-provider-metal3PR 3319
- metal3-io/cluster-api-provider-metal3PR 3322
- metal3-io/cluster-api-provider-metal3PR 3323
- metal3-io/cluster-api-provider-metal3PR 3325
- metal3-io/cluster-api-provider-metal3PR 3327
- metal3-io/cluster-api-provider-metal3PR 3343
- metal3-io/cluster-api-provider-metal3PR 3344
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- github.com/metal3-io/cluster-api-provider-metal3/pull/3288
- github.com/metal3-io/cluster-api-provider-metal3/pull/3294
- github.com/metal3-io/cluster-api-provider-metal3/pull/3317
- github.com/metal3-io/cluster-api-provider-metal3/pull/3319
- github.com/metal3-io/cluster-api-provider-metal3/pull/3322
- github.com/metal3-io/cluster-api-provider-metal3/pull/3323
- github.com/metal3-io/cluster-api-provider-metal3/pull/3325
- github.com/metal3-io/cluster-api-provider-metal3/pull/3327
- github.com/metal3-io/cluster-api-provider-metal3/pull/3343
- github.com/metal3-io/cluster-api-provider-metal3/pull/3344
- github.com/metal3-io/cluster-api-provider-metal3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.