# CVE-2026-75569: Mce-operator-bundle: all github actions pinned by mutable tag, not commit sha

> Attackers with repository write access can inject malicious code into the build process by exploiting unpinned GitHub Actions tags, compromising the distributed software.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/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:** 19 Aug 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-77qj-pc4h-hxwh

## What is CVE-2026-75569?

CVE-2026-75569 is a high-severity vulnerability in Red Hat multicluster engine for Kubernetes 2.10, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in mce-operator-bundle. The build process fetches and executes scripts from a remote repository without performing integrity checks, such as commit pinning or signature verification. This allows a malicious actor with write access to the remote repository to inject and execute arbitrary code during the build. The consequence is a compromised build process, potentially leading to the distribution of malicious software.

Weakness: CWE-1357 (Reliance on Insufficiently Trustworthy Component)

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


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

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

## Is CVE-2026-75569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75569 is a high-severity vulnerability in Red Hat multicluster engine for Kubernetes 2.10, published on 19 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-75569 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-75569/ (Markdown: https://insights.sbomify.com/CVE-2026-75569/index.md)
```

## Sources

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

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