# CVE-2026-73267: Missing authorization in multicluster engine for Kubernetes 2.10

> A tenant can delete any ManagedCluster, including the hub's local cluster, by manipulating the ClusterClaim namespace field due to missing ownership checks.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-q3cg-8r2r-6g4g

## What is CVE-2026-73267?

CVE-2026-73267 is a high-severity missing authorization vulnerability in Red Hat multicluster engine for Kubernetes 2.10, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

## Which versions are affected by CVE-2026-73267?


## How do I fix CVE-2026-73267?

No fix has been published for CVE-2026-73267 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73267 being exploited?

There is no known exploitation of CVE-2026-73267 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73267 and fix it if it is affected.

What it is: CVE-2026-73267 is a high-severity missing authorization vulnerability in Red Hat multicluster engine for Kubernetes 2.10, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73267 in the wild and no public exploit code.

Affected product: Red Hat multicluster engine for Kubernetes 2.10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73267/ (Markdown: https://insights.sbomify.com/CVE-2026-73267/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73267
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73267
- OSV: https://osv.dev/vulnerability/CVE-2026-73267

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73267/
Summaries are generated and may contain mistakes; the official description above is the record.