Multicloud-integrations: multicloud-integrations: pull-model propagation allows hub tenant to target arbitrary spoke cluster via unvalidated ocm-managed-cluster annotation (CVE-2026-72526)

Why this deserves its current priority

CVSS is 9.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 12, 2026

Sources and claim methodology

Upstream source description

A flaw was found in the multicloud-integrations component. The Application propagation controller processes the `ocm-managed-cluster` annotation from an Application Custom Resource (CR) without proper validation. A tenant with permissions to create Applications on the hub cluster can exploit this to target arbitrary managed clusters. This can force ArgoCD on the spoke clusters to synchronize attacker-controlled manifests, leading to arbitrary code execution or privilege escalation on those clusters.

Quoted source text, attributed separately from HOL analysis.