# CVE-2026-75924: Privilege escalation in Multicluster Engine for Kubernetes

> Compromised addon-manager pods can read all secrets and approve CSRs due to excessive ClusterRole permissions, enabling privilege escalation.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-9h7q-h45w-4hxq

## What is CVE-2026-75924?

CVE-2026-75924 is a high-severity vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in managed-serviceaccount. A compromised addon-manager pod, due to its ClusterRole granting excessive permissions, can read any secret across all namespaces. Additionally, it can approve arbitrary Certificate Signing Requests (CSRs), which could lead to information disclosure and privilege escalation within the cluster.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-75924 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75924 is a high-severity vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75924 in the wild and no public exploit code.

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

## Sources

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

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