What is the CVSS score of EUVD-2026-57058?

EUVD-2026-57058 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 23.0%.

Which versions of Red Hat ACM are affected by EUVD-2026-57058?

Red Hat Advanced Cluster Management for Kubernetes 2 (RHACM) contains a critical vulnerability (CVE-2026-70398, CVSS 9.6) that allows authenticated users to steal credentials granting unauthorized…

How to fix or mitigate EUVD-2026-57058?

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. Within 7 days, implement comprehensive audit logging for bearer-token usage, establish alerting on suspicious token access patterns, rotate all managed cluster service account credentials, and enforce RBAC denials on cross-namespace GitOpsCluster operations. Within 30 days, establish a formal escalation process with Red Hat to track patch availability, develop and test upgrade procedures for RHACM 2, and evaluate alternative cluster management platforms if no patch timeline is provided beyond 60 days.

Red Hat ACM EUVD-2026-57058

| CVE-2026-70398 CRITICAL

Unintended Proxy or Intermediary ('Confused Deputy') (CWE-441)

2026-08-12 redhat

GHSA-cjw2-r57r-pwvf

Authentication Bypass Red Hat Red Hat Advanced Cluster Management For Kubernetes 2 Red Hat

9.6

CVSS 3.1 · Vendor: redhat

Severity by source

Vendor (redhat) PRIMARY

9.6 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

vuln.today AI

9.6 CRITICAL

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.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:N/SA:N

Red Hat

9.6 HIGH

qualitative

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 12, 2026 - 02:01 vuln.today

CVE Published

Aug 12, 2026 - 01:10 cve.org

CRITICAL 9.6

DescriptionCVE.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. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the CVSS base score is 9.6 (Critical).

Technical ContextAI

RHACM is Red Hat's hub-and-spoke multicluster management platform; the multicloud-integrations component integrates OpenShift GitOps/ArgoCD so that applications can be deployed from a central hub to managed 'spoke' clusters. The GitOpsCluster controller reconciles cluster credentials - spoke-cluster bearer tokens stored as Kubernetes Secrets - so ArgoCD can authenticate to remote clusters. The root cause is CWE-441 (Unintended Proxy or Intermediary / 'Confused Deputy'): the controller performs a privileged action (copying/placing a sensitive Secret) using the tenant's untrusted input to decide the destination namespace, without properly validating that the requesting tenant is authorized for that source token or destination. This lets attacker-controlled input steer a privileged reconciliation operation, and the resulting token exposure undermines ArgoCD AppProject boundaries that are supposed to isolate what each tenant can deploy and to which clusters.

RemediationAI

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. As compensating controls until patched: restrict who can create or modify GitOpsCluster custom resources via RBAC so untrusted tenants cannot drive the controller (trade-off: may block legitimate self-service GitOps onboarding); tighten ArgoCD AppProject and namespace RBAC so tenants cannot read Secrets outside their own namespace (trade-off: requires careful policy review to avoid breaking existing app deployments); and audit for GitOpsCluster resources whose destination namespaces do not match the requesting tenant, plus rotate any spoke-cluster bearer tokens suspected of exposure (trade-off: token rotation can disrupt in-flight ArgoCD syncs to managed clusters). Consider limiting the GitOpsCluster controller/multicloud-integrations to trusted operators only in genuinely multi-tenant hubs.