# CVE-2026-110744: A flaw was found in multicluster-global-hub-operator-bundle.


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-34hq-mjq7-9mgx

## What is CVE-2026-110744?

CVE-2026-110744 is a high-severity vulnerability in Red Hat Multicluster Global Hub, published on 21 Oct 2026. 

### Official description

A flaw was found in multicluster-global-hub-operator-bundle. The operator is configured with overly broad role-based access control (RBAC) permissions that grant cluster-wide impersonation of arbitrary users, groups, and service accounts without restriction. An attacker who compromises the operator or obtains its service account credentials can exploit this flaw to achieve privilege escalation, gaining full administrative control over the cluster.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-110744 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110744 is a high-severity vulnerability in Red Hat Multicluster Global Hub, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110744 in the wild and no public exploit code.

Affected product: Red Hat Multicluster Global Hub. 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-110744/ (Markdown: https://insights.sbomify.com/CVE-2026-110744/index.md)
```

## Sources

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

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