Skip to main content
VulnerabilityPublished Updated

CVE-2026-72526: Red Hat Advanced Cluster Management for Kubernetes 2.11 · Confused Deputy

Affects Red Hat Advanced Cluster Management for Kubernetes 2.11Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17Affected–Fixed in–

AI-suggested

Currently, Red Hat states that no mitigation or fix is available that meets their criteria for ease of use, applicability, and stability. Users should monitor the Red Hat advisory for updates. Until an official fix or mitigation is released, restricting Application creation permissions to trusted users and minimizing the attack surface are recommended as interim risk reduction measures.

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.

References

Community reviews

Loading reviews…