# CVE-2026-71567: User-controlled variables inserted unescaped into shell scripts and Kubernetes manifests

> Attackers can execute arbitrary commands via unescaped variables in shell scripts and Kubernetes manifests within OpenShift Metal3 fakefish.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-xfhv-fp7q-v2cc

## What is CVE-2026-71567?

CVE-2026-71567 is a high-severity command injection vulnerability in openshift-metal3 fakefish, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In openshift-metal3/fakefish there is a repeated pattern in some of the scripts where shell variables
 are injected without quoting them either into command lines or into 
manifests. This mostly applies to the Image URL and BMC credentials 
(which are not verified by FakeFish).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-71567 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71567 is a high-severity command injection vulnerability in openshift-metal3 fakefish, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71567 in the wild and no public exploit code.

Affected product: openshift-metal3 fakefish. 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-71567/ (Markdown: https://insights.sbomify.com/CVE-2026-71567/index.md)
```

## Sources

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

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