CVE-2026-70398: Red Hat Advanced Cluster Management for Kubernetes 2.11 · Confused Deputy
Affects Red Hat Advanced Cluster Management for Kubernetes 2.11Source CVE Database V5
Not known to be exploited · CVSS 9.6 Critical.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 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 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17 | Affected– | Fixed in– |
AI-suggested
Currently, no mitigation or patch meets Red Hat Product Security's criteria for ease of use, applicability, or stability. Users should monitor Red Hat's advisory for updates. Customers with a Technical Account Manager (TAM) or RHEL Security Select Add-on can consult directly with Red Hat for guidance. Until a fix is available, restricting tenant privileges and monitoring for suspicious activity related to GitOpsCluster controller operations may help reduce risk, but no official mitigation is provided.
Description
A flaw was found in multicloud-integrations, a component of Red Hat Advanced Cluster Management (RHACM). This vulnerability allows an authenticated user, referred to as a tenant, to manipulate the GitOpsCluster controller. By exploiting this, a tenant can redirect sensitive spoke cluster bearer tokens from secure locations to a namespace they control. This unauthorized access to tokens can lead to the disclosure of critical information and bypass security policies within ArgoCD AppProjects.
References
- access.redhat.com/security/cve/CVE-2026-70398 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2514228 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60386 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60389 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60390 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60387 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60388 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60391 (opens in a new tab)