openshift-metal3 fakefish: unquoted shell variables in the Redfish shim allow command injection

CVE-2026-71567Firmware, BMC & network fabriccurated

Impact

fakefish is the shim bare-metal OpenShift deployments put in front of hardware whose BMC has no usable Redfish implementation: it accepts Redfish calls from the provisioning controller and turns them into vendor-specific BMC operations. Several of its scripts interpolate shell variables into command lines and manifests without quoting, and the values reaching those scripts include the boot image URL and the BMC credentials, neither of which fakefish validates. Someone who can drive those inputs can inject shell metacharacters and execute commands on the host running fakefish - the host that holds credentials for every machine it provisions, sitting on the out-of-band path to a rack of nodes. CVSS records a changed scope and high integrity impact with no confidentiality loss, consistent with command execution that reaches beyond the shim itself. Provisioning hosts are usually rebuilt rarely and trusted broadly, which is what makes this worth more than its score suggests.

Who can reach it

Authenticated but low-privileged, over the network (AV:N/PR:L): anyone who can reach the fakefish endpoint on the provisioning or management network, or who can set the image URL or BMC credentials that the provisioning flow hands to it - for example through a BareMetalHost definition.

What to do

Follow the project advisory GHSA-xfhv-fp7q-v2cc; the record names no fixed release. fakefish is deployed by running the repository's scripts, so remediating means pulling the corrected scripts and restarting the fakefish service - no node drain and no firmware work. Until that is done, keep the endpoint off any tenant-reachable network and treat image URLs and BMC credentials as untrusted input.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-71567 https://github.com/openshift-metal3/fakefish/security/advisories/GHSA-xfhv-fp7q-v2cc

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.