Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

  1. ID reserved

    By redhat

  2. · 5 days later

    Published

  3. · 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

CVSS scores of CVE-2025-2241, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
NVDNVD · Deferred3.1High8.2CVSS: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
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

Affected packages

From reviewed advisories of the GitHub Advisory Database.

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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-2241 badge
[![CVE-2025-2241](https://cveledger.app/badge/CVE-2025-2241.svg)](https://cveledger.app/cve/CVE-2025-2241)

Record last updated .