# CVE-2026-92092: A flaw was found in openshift-ansible.


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-vhfq-9q32-q69f

## What is CVE-2026-92092?

CVE-2026-92092 is a high-severity vulnerability in Red Hat OpenShift Container Platform 4, published on 29 Oct 2026. 

### Official description

A flaw was found in openshift-ansible. The installer container's `run` script downloads and executes remote inventory and dynamic scripts without integrity verification. A remote attacker, by performing a Man-in-the-Middle (MITM) attack or compromising the HTTP server providing these scripts, could substitute an arbitrary executable. This malicious executable would then run with the installer's user ID (UID) and full cluster-provisioning privileges, leading to arbitrary code execution.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

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

## Is CVE-2026-92092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92092 is a high-severity vulnerability in Red Hat OpenShift Container Platform 4, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92092 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Container Platform 4. 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-92092/ (Markdown: https://insights.sbomify.com/CVE-2026-92092/index.md)
```

## Sources

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

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