CVE-2025-2241: hive · Insecure Storage of Sensitive Information
Affects hiveSource GCVE Database
Not known to be exploited · CVSS 8.2 High.
Data as of 31 Oct 2026, 08:20 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 8.2 |
|---|
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hive | Affected
| Fixed in– |
AI-suggested
Red Hat recommends the following mitigations: 1) Restrict read access to ClusterProvision objects to only trusted users with valid VCenter credentials by verifying permissions using 'oc adm policy who-can get clusterprovision' and 'oc adm policy who-can read clusterprovision'. 2) Immediately rotate VCenter credentials to revoke any unauthorized access. 3) Conduct a security audit of VCenter users and roles to detect unauthorized access or configuration changes and take remediation actions as needed.
Description
CVE-2025-2241 is a vulnerability in Hive, a component of Multicluster Engine (MCE) and Advanced Cluster Management (ACM), where VCenter credentials are exposed in the ClusterProvision object after provisioning a VSphere cluster. Users with read access to ClusterProvision objects can extract these sensitive credentials even without direct access to Kubernetes Secrets. This exposure can lead to unauthorized VCenter access, cluster management, and privilege escalation.