CVE-2026-27211

CRITICALNVD 10.010.0
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Trending — 3 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
10.0
EG Score
10.0(low)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
40%
KEV
Not listed

Published

February 21, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Host File Exfiltration via QCOW Backing File Abuse · Advisory · cloud-hypervisor/cloud-hypervisor · GitHub

https://github.com/cloud-hypervisor/cloud-hypervisor/security/advisories/GHSA-jmr4-g2hv-mjj6
github_release Patch Available

v51.0

Patch available: cloud-hypervisor/cloud-hypervisor v51.0

https://github.com/cloud-hypervisor/cloud-hypervisor/releases/tag/v51.0
github_release Patch Available

v50.1

Patch available: cloud-hypervisor/cloud-hypervisor v50.1

https://github.com/cloud-hypervisor/cloud-hypervisor/releases/tag/v50.1
github_commit

commit cb495959a8be (cloud-hypervisor/cloud-hypervisor)

Fix landed in cloud-hypervisor/cloud-hypervisor commit cb495959a8be — awaiting tagged release

https://github.com/cloud-hypervisor/cloud-hypervisor/commit/cb495959a8bea1b56e8fc82d15ba527a0e7fcf3c
github_commit

commit a63315df54e0 (cloud-hypervisor/cloud-hypervisor)

Fix landed in cloud-hypervisor/cloud-hypervisor commit a63315df54e0 — awaiting tagged release

https://github.com/cloud-hypervisor/cloud-hypervisor/commit/a63315df54e06f6ec867f17b63076c266e2d8648
github_commit

commit 509832298b68 (cloud-hypervisor/cloud-hypervisor)

Fix landed in cloud-hypervisor/cloud-hypervisor commit 509832298b68 — awaiting tagged release

https://github.com/cloud-hypervisor/cloud-hypervisor/commit/509832298b6865365b00bda88722e76e41ce7f41
github_commit

commit 081a6ebb5184 (cloud-hypervisor/cloud-hypervisor)

Fix landed in cloud-hypervisor/cloud-hypervisor commit 081a6ebb5184 — awaiting tagged release

https://github.com/cloud-hypervisor/cloud-hypervisor/commit/081a6ebb5184228ff348601502258f3f72bd8b43

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:10 UTCEG score recompute
  2. 2026-07-27 14:10 UTCVendor advisory
  3. 2026-07-27 13:55 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-27211?
CVE-2026-27211 is a critical vulnerability published on February 21, 2026. 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…
When was CVE-2026-27211 disclosed?
CVE-2026-27211 was first published in the National Vulnerability Database on February 21, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27211 actively exploited?
CVE-2026-27211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 60.1% of all scored CVEs.
What is the CVSS score of CVE-2026-27211?
CVE-2026-27211 has a CVSS v3 base score of 10.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-27211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-27211

Explore →

Is Your Infrastructure Affected by CVE-2026-27211?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs