Multicluster Engine for Kubernetes: Insecure Storage of Sensitive Information
CVE-2025-2241 is a high-severity insecure storage of sensitive information vulnerability in Multicluster Engine for Kubernetes from Red Hat, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Multicluster Engine for Kubernetes you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Multicluster Engine for Kubernetes | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N. Scored by CNA (redhat.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insecure Storage of Sensitive Information
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
More Insecure Storage of Sensitive Information vulnerabilities (CWE-922)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Other vulnerabilities in Multicluster Engine for Kubernetes
- 8.3 High severity
- 8.8 High severity
- 8.7 High severity
- 9.4 Critical severity
- 8.1 High severity
- 7.2 High severity
Recent Insecure Storage of Sensitive Information vulnerabilities
- 7.5 High severity
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 8.2 High severity
Spotted an error? Tell us.