CVE-2026-75924: Red Hat Multicluster Engine for Kubernetes · Improper Privilege Management
Affects Red Hat Multicluster Engine for KubernetesSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
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 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatMulticluster Engine for Kubernetes | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2 | Affected– | Fixed in– |
AI-suggested
As per the Red Hat advisory, no mitigation or fix currently meets the criteria for deployment and stability. Users should monitor the Red Hat advisory for updates. Customers with a Technical Account Manager (TAM) can review this CVE directly with their TAM for tailored guidance. Until an official fix or mitigation is released, organizations should consider limiting exposure of the addon-manager pod and monitor for suspicious activity related to secret access and CSR approvals.
Description
A flaw was found in managed-serviceaccount. A compromised addon-manager pod, due to its ClusterRole granting excessive permissions, can read any secret across all namespaces. Additionally, it can approve arbitrary Certificate Signing Requests (CSRs), which could lead to information disclosure and privilege escalation within the cluster.