Loading vulnerability…
CVE-2025-29781 is an authorization flaw in Metal3 Bare Metal Operator (BMO)'s namespace-scoped BMCEventSubscription custom resource. Before BMO versions 0.8.1 and 0.9.1, BMCEventSubscription could reference an httpHeadersRef Secret in an arbitrary Kubernetes namespace. A tenant-level Kubernetes account could create the resource in a namespace it controls and cause the BMO controller, when granted cluster-scoped permissions, to read a Secret from an unauthorized namespace and expose it in the attacker's namespace. The corrected releases validate that a referenced Secret is in the same namespace as the corresponding BareMetalHost, reject invalid resources during admission, and prevent the controller from reading invalid pre-existing references.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in the Bare Metal Operator API through which the BMCEventSubscription custom resource can expose secrets from other Kubernetes namespaces.
An authorization or secret-exposure vulnerability in Bare Metal Operator (BMO) whereby the BMCEventSubscription CRD can expose secrets from other namespaces.
An information-disclosure vulnerability in the Bare Metal Operator API that can expose secrets from other namespaces through the BMCEventSubscription custom resource definition.
A vulnerability in Bare Metal Operator APIs through which the BMCEventSubscription custom resource can expose secrets from other namespaces.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.