# CVE-2026-76139: Supply chain in Red Hat Advanced Cluster Management for Kubernetes 2.11

> Attackers can inject malicious code via unpinned remote scripts during build, compromising operator bundles and exposing build credentials.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 16 Oct 2026
- **Also known as:** GHSA-37hx-9chj-hc3m

## What is CVE-2026-76139?

CVE-2026-76139 is a high-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11, 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 acm-operator-bundle. The build process for this component downloads and runs a script from a remote source without verifying its authenticity or integrity. This script gains access to sensitive credentials, such as GitHub access tokens and registry passwords, used in the build environment. A remote attacker could exploit this vulnerability to inject malicious code, leading to unauthorized access to build resources and potential compromise of the resulting operator bundle.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-76139 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76139 is a high-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11, 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-76139 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Management for Kubernetes 2.11. 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-76139/ (Markdown: https://insights.sbomify.com/CVE-2026-76139/index.md)
```

## Sources

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

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