Two critical security vulnerabilities have been discovered in the Xen hypervisor, potentially allowing a malicious virtual machine (VM) to read and modify the memory of other virtual machines running on the same host. The vulnerabilities could also expose Dom0, the privileged management domain responsible for controlling other virtual machines. This creates a serious security risk for environments that depend on Xen to keep multiple virtual machines isolated from one another. The Xen Project released security patches on November 3, 2026, and confirmed that no known mitigation is currently available.
The issue is related to a Xen feature called Grant Copy, which allows virtual machines to exchange data through approved memory pages. To improve performance, Xen temporarily stores previously checked information so it does not have to repeat the same permission checks for every memory operation. However, researchers found that the validation process does not work correctly in certain situations. As a result, a malicious guest VM can bypass memory access restrictions and interact with memory that belongs to other virtual machines.
The security issues are tracked as CVE-2026-102703 and CVE-2026-102704, and are documented under Xen Security Advisory XSA-523. The first vulnerability involves incorrect handling of frame numbers and grant references, which can cause Xen to mix up memory references. The second vulnerability occurs because a security check restricting certain memory-copy operations to a VM’s own memory was placed incorrectly. According to the Xen Project, all Xen versions from 4.6 onwards are affected, while versions 4.5 and earlier are not vulnerable.
The discovery of these vulnerabilities also highlights the growing role of artificial intelligence in cybersecurity research. The Xen Project credited Anthropic with discovering the issues using its Claude AI model, while Stephan Lipp from Ada Logics independently validated the findings. The CodeAnt AI Security Research Team later reported the same security issue independently. The Xen advisory does not report any confirmed attacks exploiting these vulnerabilities or specify the exact level of access an attacker needs inside a guest VM to exploit them.
The vulnerabilities have raised concerns for several platforms that rely on Xen-based virtualization. XCP-ng, an open-source virtualization platform, warned that a compromised guest VM could escape its isolation and potentially take control of the entire host system. Qubes OS also confirmed that all its supported releases and configurations are affected because it uses Xen to separate applications and activities into isolated environments. Debian’s security tracker also listed affected Xen packages in its Bookworm, Trixie and Forky releases, while its Sid release was listed as fixed as of November 4.
The Xen Project has released patches to address both vulnerabilities and recommends applying the appropriate updates as soon as possible. XCP-ng 8.3 users can install the updated Xen package, version xen-4.17.7-4.2.xcpng8.3, but a host reboot is required for the fix to take effect. Qubes OS 4.3 users need Xen package version 4.19.6-3 in Dom0, followed by a Dom0 restart. Since there is no known workaround, administrators should check their virtualization platforms, install the security updates provided by their vendors and ensure that all affected systems are properly patched.
Stay alert, and keep your security measures updated!
Source: Follow cybersecurity88 on X and LinkedIn for the latest cybersecurity news
