CVE-2025-2241Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm
- 8.2HighCVSS base score
- 0.50%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By redhat
- 5 days later
· 5 days later
Published
- 20 months later
· 20 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhatCNA (assigner) | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N |
| NVDNVD · Deferred | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.50% · top 57% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.
Affected products
hive
- affected 1.2.4105-7735bf3 – ≤ 1.1.16
Red Hat · Multicluster Engine for Kubernetes
All versions: affected
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2
All versions: affected
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- Gogithub.com/openshift/hiveGHSA-c339-mwfc-fmr2 (opens in a new tab)
What to do
Workaround: 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 activity is found, revoke access by rotating credentials again (step 2) and taking necessary remediation actions.
References
References3
- https://access.redhat.com/security/cve/CVE-2025-2241 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2351350 (opens in a new tab)issue-trackingx_refsource_REDHAT
- https://github.com/openshift/hive/pull/2612 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-6523 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-c339-mwfc-fmr2 (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-2241)Record last updated .