Bug 2514228 (CVE-2026-70398) - CVE-2026-70398 multicloud-integrations: multicloud-integrations: GitOpsCluster.spec.argoServer.argoNamespace writes spoke bearer tokens to attacker-chosen namespace
Summary: CVE-2026-70398 multicloud-integrations: multicloud-integrations: GitOpsCluste...
Keywords:
Status: NEW
Alias: CVE-2026-70398
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-11 17:38 UTC by OSIDB Bzimport
Modified: 2026-08-12 17:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-11 17:38:49 UTC 
A flaw was found in the multicloud-integrations component of Red Hat Advanced Cluster Management (RHACM). The GitOpsCluster controller uses the tenant-controlled spec.argoServer.argoNamespace field to determine where spoke cluster bearer token Secrets are written. The controller copies ManagedServiceAccount tokens from privileged managed-cluster hub namespaces into the attacker-specified namespace. The only guard (VerifyArgocdNamespace) is bypassed by a tenant-settable annotation on the same CR. A tenant can exfiltrate spoke bearer tokens and bypass ArgoCD AppProject constraints.

Upstream repo: https://github.com/stolostron/multicloud-integrations
Audited commit: d88a168
Jira tracker: ACM-38644
Note You need to log in before you can comment on or make changes to this bug.