CVE-2025-2241: Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm

Published Mar 11, 2025
·
Updated

A flaw was found in Hive, a component of Multicluster Engine (MCE) and Advanced Cluster Management (ACM). This vulnerability causes VCenter credentials to be exposed in the ClusterProvision object after provisioning a VSphere cluster. Users with read access to ClusterProvision objects can extract sensitive credentials even if they do not have direct access to Kubernetes Secrets. This issue can lead to unauthorized VCenter access, cluster management, and privilege escalation.

Other sources

Using hive (including via MCE or ACM) to provision a VSphere cluster requires supplying VCenter credentials via a Secret in the same namespace as the ClusterDeployment that declares the desired configuration of the cluster. These credentials are echoed back once the cluster is provisioned via the ClusterProvision object that hive creates in the same namespace. It is likely that customers don't realize this, and may have RBAC allowing ClusterProvision read access to users who would otherwise not be trusted with VCenter credentials.

Red Hat

Affected Software

4 affected components
Red Hat Hive
Red Hat Multicluster Engine
Red Hat Advanced Cluster Management
go/github.com/openshift/hive<=1.1.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Restrict RBAC read access to ClusterProvision objects (and related Hive/ClusterProvision resources) so only trusted users/service accounts can read them, to prevent extraction of exposed vCenter credentials echoed into ClusterProvision after provisioning.

Event History

Mar 11, 2025
Data Sourced
via Red Hat·12:50 PM
DescriptionSeverityAffected Software
Mar 17, 2025
CVE Published
via MITRE·04:27 PM
Data Sourced
via MITRE·04:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-2241?

CVE-2025-2241 has a high severity due to the exposure of sensitive VCenter credentials.

2

How do I fix CVE-2025-2241?

To fix CVE-2025-2241, update Red Hat Hive, Multicluster Engine (MCE), and Advanced Cluster Management (ACM) to the latest patched versions.

3

What systems are affected by CVE-2025-2241?

CVE-2025-2241 affects Red Hat Hive, Multicluster Engine (MCE), and Advanced Cluster Management (ACM) software.

4

How does CVE-2025-2241 impact security?

CVE-2025-2241 impacts security by potentially allowing unauthorized access to VCenter credentials.

5

When was CVE-2025-2241 disclosed?

CVE-2025-2241 was disclosed on 2025-03-10.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203