multicluster engine for Kubernetes 2.1: Incorrect Privilege Assignment
CVE-2026-10059 is a critical-severity incorrect privilege assignment vulnerability in multicluster engine for Kubernetes 2.1 from Red Hat, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.64% chance of exploitation within 30 days, higher than 51% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of multicluster engine for Kubernetes 2.1 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 2.1 | Not specified in the record | Not stated |
| Red Hat | multicluster engine for Kubernetes 2.11 | Not specified in the record | Not stated |
| Red Hat | multicluster engine for Kubernetes 2.6 | Not specified in the record | Not stated |
| Red Hat | multicluster engine for Kubernetes 2.8 | Not specified in the record | Not stated |
| Red Hat | multicluster engine for Kubernetes 2.9 | 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
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- 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
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (redhat.com).
Official description
A flaw was found in the Multicluster Engine for Kubernetes ClusterCurator controller. A tenant administrator with namespace-scoped privileges can exploit this vulnerability by creating a namespaced ClusterCurator. This action inadvertently grants the tenant administrator the ability to mint a token for a ServiceAccount with cluster-wide administrative authority. This leads to a privilege escalation, allowing the tenant administrator to gain full control over the cluster.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Privilege Assignment
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
More Incorrect Privilege Assignment vulnerabilities (CWE-266)
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
Other references
Other vulnerabilities in multicluster engine for Kubernetes 2.1
- 9.4 Critical severity
- 9.3 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.7 High severity
- 8.7 High severity
Recent Incorrect Privilege Assignment vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 8.0 High severity
- 8.8 High severity
- 9.3 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.