<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xen-Hypervisor on CuraSec</title><link>https://curasec.metacog.co.kr/tags/xen-hypervisor/</link><description>Recent content in Xen-Hypervisor on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 04 Nov 2026 18:40:06 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/xen-hypervisor/index.xml" rel="self" type="application/rss+xml"/><item><title>Xen Hypervisor Flaws Allow Cross-VM Memory Read/Write Including dom0</title><link>https://curasec.metacog.co.kr/insights/2026-11-04-xen-hypervisor-flaws-let-one-malicious-vm-read-and-write-any/</link><pubDate>Wed, 04 Nov 2026 18:40:06 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-11-04-xen-hypervisor-flaws-let-one-malicious-vm-read-and-write-any/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> VM isolation is completely broken on all Xen ≥4.6: a malicious guest can read and write memory of any co-resident VM, including dom0. No mitigation exists — patch to the fixed Xen release immediately; treat any multi-tenant Xen host as potentially compromised if untrusted VMs run on it.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If your environment or any IaaS vendor you rely on runs Xen-based hypervisors (Citrix, legacy AWS, XCP-ng), verify patching timelines this quarter — a compromised guest VM gaining full dom0 access could break tenant-data isolation and trigger disclosure obligations.&lt;/li>
&lt;/ul></description></item></channel></rss>