EUVD-2026-57058
GHSA-cjw2-r57r-pwvf
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Authenticated tenant (PR:L) reaches the hub API over the network (AV:N/AC:L) and abuses a controller crossing namespace/cluster trust boundaries (S:C) to disclose tokens and bypass policy (C:H/I:H); no availability impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Cross-tenant bearer-token disclosure in Red Hat Advanced Cluster Management for Kubernetes 2 (RHACM) lets an authenticated tenant abuse the GitOpsCluster controller in the multicloud-integrations component to redirect spoke-cluster credentials into a namespace they control. Because the controller acts on the tenant's behalf across trust boundaries (a confused-deputy flaw), a low-privileged user can obtain tokens that grant access to managed spoke clusters and bypass ArgoCD AppProject scoping controls. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires an authenticated RHACM tenant account on the hub with permission to create or modify GitOpsCluster custom resources in the multicloud-integrations/OpenShift GitOps integration; the deployment must be a shared/multi-tenant GitOps setup where spoke-cluster bearer tokens are managed by the GitOpsCluster controller and ArgoCD AppProjects are used for tenant isolation. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are moderately consistent toward high priority: the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) describes a network-reachable, low-complexity attack needing only low privileges and no user interaction, with a scope change reflecting that the compromised hub controller yields access to separate spoke clusters - appropriate for a confused-deputy token-theft flaw. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A legitimate but low-privileged tenant on a shared RHACM hub creates or edits a GitOpsCluster resource so that the controller writes a spoke cluster's bearer-token Secret into a namespace the tenant fully controls. The tenant then reads the Secret and uses the token to authenticate directly to the managed spoke cluster and to deploy outside their permitted ArgoCD AppProject scope. … |
| Remediation | No vendor-released patch version is identified in the available data, so monitor Red Hat's advisory at https://access.redhat.com/security/cve/CVE-2026-70398 and the associated errata (referenced from Bugzilla 2514228) and apply the fixed multicloud-integrations/RHACM build for your 2.x channel as soon as it is published - that is the primary fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit all RHACM 2 deployments and inventory multicloud-integrations components; immediately restrict GitOpsCluster controller access through RBAC to only essential service accounts and disable the feature entirely if unused, then configure network policies to isolate the controller pod from untrusted tenant namespaces. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Cross-cluster remote code execution in Red Hat Advanced Cluster Management for Kubernetes 2 (multicloud-integrations / A
Unauthorized cross-tenant Secret and ConfigMap access in the multicloud-operators-channel component of Red Hat Advanced
Secret exfiltration across Kubernetes namespace boundaries in the multicloud-operators-subscription component of Red Hat
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 lets a namespace-scoped tenant abuse the mu
Privilege escalation in Red Hat Advanced Cluster Management's multicloud-operators-subscription controller lets a low-pr
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 stems from the search-v2-operator being bou
Cross-cluster traffic interception in Submariner (shipped within Red Hat Advanced Cluster Management for Kubernetes 2) a
Cross-cluster remote code execution in Red Hat Advanced Cluster Management for Kubernetes 2 (acm-search-v2-rhel9 search
Cross-namespace Secret manipulation in the multicloud-operators-channel component of Red Hat Advanced Cluster Management
Command and SQL injection in Red Hat Advanced Cluster Management for Kubernetes 2 (acm-search-v2-rhel9) lets a privilege
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 allows any attacker with local pod executio
Excessive ClusterRole permissions on the managed-serviceaccount addon-manager pod in Red Hat Advanced Cluster Management
Same technique Authentication Bypass
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today