CVE-2026-73267 json
Clusterclaims-controller: managedcluster deletion keyed solely on clusterclaim.spec.namespace with no local ownership check
published 2026-08-21 2 mo ago modified 2026-10-26 14 d ago also EUVD-2026-63800
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
A flaw was found in the clusterclaims-controller component of multicluster engine (MCE). A tenant with standard permissions to create and delete ClusterClaim resources can exploit this by manipulating the `spec.namespace` field. This allows the tenant to specify and delete any ManagedCluster, including the hub's local-cluster or other tenants' clusters, due to a missing ownership check. This vulnerability can lead to a denial of service by enabling unauthorized deletion of ManagedClusters.
Patch / fix
- Red Hat multicluster engine for Kubernetes 2.10 1787196014
- Red Hat multicluster engine for Kubernetes 2.11 1787239442
- Red Hat multicluster engine for Kubernetes 2.17 1786577950
- Red Hat multicluster engine for Kubernetes 2.6 1787259112
- Red Hat multicluster engine for Kubernetes 2.8 1787259059
- Red Hat multicluster engine for Kubernetes 2.9 1787195995
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-73267 updated cvss 7.7
clusterclaims-controller: ManagedCluster deletion keyed solely on ClusterClaim.Spec.Namespace with no local ownership check
-
Red Hat multicluster engine for Kubernetes 2.6 multicluster-engine/clusterclaims-controller-rhel9 1787259112fixed: vendor fix RHSA-2026:59579
-
Red Hat multicluster engine for Kubernetes 2.8 multicluster-engine/clusterclaims-controller-rhel9 1787259059fixed: vendor fix RHSA-2026:59558
-
Red Hat multicluster engine for Kubernetes 2.9 multicluster-engine/clusterclaims-controller-rhel9 1787195995fixed: vendor fix RHSA-2026:59559
-
Red Hat multicluster engine for Kubernetes 2.10 multicluster-engine/clusterclaims-controller-rhel9 1787196014fixed: vendor fix RHSA-2026:59557
-
Red Hat multicluster engine for Kubernetes 2.11 multicluster-engine/clusterclaims-controller-rhel9 1787239442fixed: vendor fix RHSA-2026:59556
-
Red Hat multicluster engine for Kubernetes 2.17 multicluster-engine/clusterclaims-controller-rhel9 1786577950fixed: vendor fix RHSA-2026:59593
-
Red Hat multicluster engine for Kubernetes 2.6 multicluster-engine/hive-rhel9 1787291123, multicluster-engine/work-rhel9 1787263188, multicluster-engine/discovery-rhel9 1787263531, multicluster-engine/placement-rhel9 1787260699, multicluster-engine/console-mce-rhel9 1787264250, multicluster-engine/must-gather-rhel9 1787264198, +20 more Red Hat multicluster engine for Kubernetes 2.8 multicluster-engine/hive-rhel9 1787291250, multicluster-engine/work-rhel9 1787259113, multicluster-engine/discovery-rhel9 1787259074, multicluster-engine/placement-rhel9 1787259108, multicluster-engine/console-mce-rhel9 1787259048, multicluster-engine/must-gather-rhel9 1787258992, +20 more Red Hat multicluster engine for Kubernetes 2.9 multicluster-engine/hive-rhel9 1787205132, multicluster-engine/work-rhel9 1786933545, multicluster-engine/discovery-rhel9 1786658519, multicluster-engine/placement-rhel9 1786491555, multicluster-engine/console-mce-rhel9 1787079359, multicluster-engine/must-gather-rhel9 1786837240, +23 more Red Hat multicluster engine for Kubernetes 2.10 multicluster-engine/hive-rhel9 1787205371, multicluster-engine/work-rhel9 1786933256, multicluster-engine/discovery-rhel9 1787071404, multicluster-engine/placement-rhel9 1786548467, multicluster-engine/console-mce-rhel9 1787079364, multicluster-engine/must-gather-rhel9 1786548899, +24 more Red Hat multicluster engine for Kubernetes 2.11 multicluster-engine/hive-rhel9 1787291933, multicluster-engine/work-rhel9 1786907276, multicluster-engine/discovery-rhel9 1786911975, multicluster-engine/placement-rhel9 1786911984, multicluster-engine/console-mce-rhel9 1787065052, multicluster-engine/must-gather-rhel9 1786911926, +25 more Red Hat multicluster engine for Kubernetes 2.17 multicluster-engine/hive-rhel9 1787033495, multicluster-engine/work-rhel9 1786933423, multicluster-engine/maestro-rhel9 1786985023, multicluster-engine/discovery-rhel9 1786681989, multicluster-engine/placement-rhel9 1786983381, multicluster-engine/console-mce-rhel9 1786668856, +28 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H |
Affected products
- Red Hat multicluster engine for Kubernetes 2.10
- Red Hat multicluster engine for Kubernetes 2.11
- Red Hat multicluster engine for Kubernetes 2.17
- Red Hat multicluster engine for Kubernetes 2.6
- Red Hat multicluster engine for Kubernetes 2.8
- Red Hat multicluster engine for Kubernetes 2.9
Classification
- Weakness
-
- CWE-602 Client-Side Enforcement of Server-Side Security
References
-
access.redhat.com
/errata/RHSA-2026:59556
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:59557
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:59558
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:59559
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:59579
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:59593
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-73267
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2514218
issue-tracking
Sources
- CVE List CVE-2026-73267
- NVD CVE-2026-73267
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.