{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27211 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-27211 is a critical path traversal vulnerability in cloud-hypervisor, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27211 and fix it if it is affected.\n\nWhat it is: CVE-2026-27211 is a critical path traversal vulnerability in cloud-hypervisor, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27211 in the wild and no public exploit code.\n\nAffected product: cloud-hypervisor. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27211/ (Markdown: https://insights.sbomify.com/CVE-2026-27211/index.md)","id":"CVE-2026-27211","markdown":"https://insights.sbomify.com/CVE-2026-27211/index.md","name":"CVE-2026-27211","record":{"aliases":["AZL-78282","GHSA-jmr4-g2hv-mjj6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Hypervisor VMM","requires_auth":"none","summary":"A malicious guest can exfiltrate arbitrary host files by abusing QCOW2 backing file detection in Cloud Hypervisor when using writable or untrusted disk images.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cloud_hypervisor","vendor":"cloudhypervisor"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cloud Hypervisor: Host File Exfiltration via QCOW Backing File Abuse","id":"CVE-2026-27211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Swiper has a Prototype Pollution Vulnerability","id":"CVE-2026-27212"},"packages":[],"prev":{"headline":"Pannellum has a XSS vulnerability in hot spot attributes","id":"CVE-2026-27210"},"products":["cloud-hypervisor"],"published":"2026-02-21","related":[{"cvss_score":4,"headline":"Malicious HTTP requests could close arbitrary opening file descriptors in cloud-hypervisor","id":"CVE-2023-30612","kev_date_added":null,"published":"2023-04-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["cloud-hypervisor"]},"summary":"A malicious guest can exfiltrate arbitrary host files by abusing QCOW2 backing file detection in Cloud Hypervisor when using writable or untrusted disk images.","url":"https://insights.sbomify.com/CVE-2026-27211/"}