CVE-2026-27211: Cloud Hypervisor: Host File Exfiltration via QCOW Backing File Abuse
Cloud Hypervisor is a Virtual Machine Monitor for Cloud workloads. Versions 34.0 through 50.0 arevulnerable to arbitrary host file exfiltration (constrained by process privileges) when using virtio-block devices backed by raw images. A malicious guest can overwrite its disk header with a crafted QCOW2 structure pointing to a sensitive host path. Upon the next VM boot or disk scan, the image format auto-detection parses this header and serves the host file's contents to the guest. Guest-initiated VM reboots are sufficient to trigger a disk scan and do not cause the Cloud Hypervisor process to exit. Therefore, a single VM can perform this attack without needing interaction from the management stack. Successful exploitation requires the backing image to be either writable by the guest or sourced from an untrusted origin. Deployments utilizing only trusted, read-only images are not affected. This issue has been fixed in version 50.1. To workaround, enable land lock sandboxing and restrict process privileges and access.
Other sources
Cloud Hypervisor: Host File Exfiltration via QCOW Backing File Abuse
— Microsoft
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-27211?
CVE-2026-27211 is classified as a moderate severity vulnerability due to the potential for arbitrary host file exfiltration.
How do I fix CVE-2026-27211?
To mitigate CVE-2026-27211, update Cloud Hypervisor to a version later than 50.0.
What versions of Cloud Hypervisor are affected by CVE-2026-27211?
CVE-2026-27211 affects Cloud Hypervisor versions 34.0 through 50.0.
What type of vulnerability is CVE-2026-27211?
CVE-2026-27211 is a host file exfiltration vulnerability that can be exploited when using virtio-block devices with raw image backing.
What components are involved in CVE-2026-27211?
CVE-2026-27211 involves the Cloud Hypervisor and its virtio-block device implementation.