CVE-2025-2241 is a high-severity (CVSS 8.2) CWE-922 vulnerability in github.com/openshift/hive. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-2241.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/openshift/hiveReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openshift/hive | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift/hive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/openshift/hive for CVE-2025-2241. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Hive is an operator which runs as a service for provisioning and perform initial configuration of OpenShift clusters. During this process users are creating instances of hive CRDs and other k8s objects, including a Secret containing credentials where Hive take these inputs and invokes openshift-install to create the…
A few mechanisms are available to reduce the risks and mitigate this vulnerability: 1. Restrict Access to ClusterProvision Objects Ensure that only trusted users with valid VCenter credentials have read access to ClusterProvision objects. This can be verified using the following commands: oc adm policy who-can get clusterprovision oc adm policy who-can read clusterprovision 2. Rotate VCenter Credentials Immediately rotate VCenter credentials to revoke access for any users who may have already accessed the exposed credentials. 3. Audit VCenter Users and Roles Conduct a security audit of VCenter accounts and roles to detect any unauthorized access or configuration changes. If any suspicious…Source: Red Hat security advisory for CVE-2025-2241 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-2241 in your dependencies?
Find it across Go, including transitive dependencies.