Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2025-29781: 0.18% estimated exploitation activity in the next 30 days; percentile 8.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

17 Mar 2025, 21:26 UTC

Last modified by the source

27 Mar 2025, 17:47 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c98h-7hp9-v9hq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-29781

Advisory: Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD
IDs: CVE-2025-29781, GHSA-c98h-7hp9-v9hq
Record: https://patchnext.com/advisories/cve-2025-29781 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/metal3-io/baremetal-operator/apis 0.9.1, 0.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/metal3-io/baremetal-operator/apis: affected >= 0.9.0, <= 0.9.0; <= 0.8.0; fixed in 0.8.1, 0.9.1

## Suggested inspection (read-only)
- Go github.com/metal3-io/baremetal-operator/apis: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/metal3-io/baremetal-operator/apis.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c98h-7hp9-v9hq (GitHub-reviewed advisory GHSA-c98h-7hp9-v9hq lists affected ranges: Go github.com/metal3-io/baremetal-operator/apis >=0.9.0 =0 <=0.8.0)

Commands are suggestions: review each one before running it.