fakefish: KubeVirt backend ignores Redfish credentials, exposing VM power and virtual media

Impact

fakefish presents a Redfish BMC interface in front of hardware that does not have a usable one, and passes the credentials it receives down to backend scripts on the assumption that a real BMC will validate them. The KubeVirt backend does not: it acts through a KUBECONFIG mounted into the container and ignores the supplied credentials completely. Anyone who can reach the fakefish endpoint therefore inherits the permissions of whoever deployed it, over the VMs that identity controls - power them on and off, and mount an arbitrary CD image. Mounting attacker-chosen boot media on a machine you can also power-cycle is a provisioning-layer compromise of the guest OS, which in a bare-metal-as-a-service GPU fleet is exactly the interface used to hand nodes between tenants.

Who can reach it

Any cluster user, or anyone else with network reach to the fakefish Redfish listener. Credentials are accepted by the interface but never checked against anything on the KubeVirt path, so this is effectively unauthenticated access to VM power control and virtual media.

What to do

The record carries only the GitHub security advisory and names no fixed version, so do not assume a released patch exists - check GHSA-qpfr-jqjq-v83w for current status before planning a window. In the meantime, restrict network access to the fakefish endpoint to the provisioning controller alone, and cut the mounted KUBECONFIG down to a dedicated service account scoped to just the VMs that instance is meant to drive, so an unauthenticated caller cannot reach beyond them. Remediation here is a redeploy of the fakefish pod, not a node action.

References

Related entries

• Linux kernel (drivers/infiniband/hw/bnxt_re): A user context could request the write-combine doorbell page repeatedlyCVE-2026-72495 · Linux kernel (drivers/infiniband/hw/bnxt_re)Critical
• Phison PS3111-S11 SSD firmware: signature check trusts a modulus carried in the image, so any firmware verifiesCVE-2026-82876 · Phison PS3111-S11 SSD controller firmware (signature verification root of trust)Critical
• Phison PS3111-S11 SSD firmware: vendor unique commands allow persistent implants in controller flashCVE-2026-84696 · Phison PS3111-S11 SSD controller firmware (vendor unique commands over ATA)Critical
• Junos OS on SRX: stack overflow in UTM Anti-Spam SBL lets a malformed DNS reply run code as rootCVE-2026-101955 · Juniper Junos OS on SRX Series (UTM Anti-Spam SBL DNS lookup)Critical
• Junos OS on SRX: SQL injection in ipfd lets a Security Intelligence feed execute code as rootCVE-2026-101997 · Juniper Junos OS on SRX Series (ipfd, Security Intelligence feed handling)Critical
• Junos OS on SRX: XML injection in utmd lets a malicious URL-feed server commit device configuration as rootCVE-2026-102037 · Juniper Junos OS on SRX Series (utmd, custom URL-feed server response parsing)Critical