Skip to main content
Public proof of conceptFix available

CVE-2025-29781

A public proof of concept exists; no exploitation attested.

  • Published2025-03-17
  • Fixed in0.9.1 · 0.8.1
  • WeaknessCWE-200 · CWE-653

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-03-1722:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-29781?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-29781?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
metal3-io/baremetal-operator/apis
BranchAffectedFixed in
0.9≥ 0.9.0, < 0.9.10.9.1
0.8< 0.8.10.8.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • RHSA-2024:11038 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.19.0 bug fix and security update

  • RHSA-2025:4677 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.13.58 bug fix and security update

  • RHSA-2025:4422 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.15.50 bug fix and security update

  • RHSA-2025:4409 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.12.76 bug fix and security update

  • RHSA-2025:4177 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.14.51 bug fix and security update

  • RHSA-2025:4008 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.16.39 bug fix and security update

2 more advisories

Full record on NVD

Fix

  1. Update metal3-io/baremetal-operator/apis to 0.9.1 · 0.8.1
  2. Vendor fix Red Hat Product Security RHSA-2024:11038 · 4 productsFor OpenShift Container Platform 4.19 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  3. Vendor fix Red Hat Product Security RHSA-2025:4677 · 1 productFor OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platfor…
  4. Vendor fix Red Hat Product Security RHSA-2025:4422 · 4 productsFor OpenShift Container Platform 4.15 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  5. Vendor fix Red Hat Product Security RHSA-2025:4409 · 1 productFor OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  6. Vendor fix Red Hat Product Security RHSA-2025:4177 · 4 productsFor OpenShift Container Platform 4.14 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  7. Vendor fix Red Hat Product Security RHSA-2025:4008 · 4 productsFor OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2025-03-18
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.16.5read 2026-10-23
  • CNAweakness (CWE)CWE-200, CWE-653read 2026-10-23
  • FIRST EPSSEPSS score0.2 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Published
2025-03-17
Last Modified
2026-06-17
NVD status
Deferred

Frequently asked questions

What is 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.

Is CVE-2025-29781 actively exploited?

A proof-of-concept exploit exists for CVE-2025-29781, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2025-29781?

CVE-2025-29781 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.

Running OpenShift Container Platform? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database