Xen Orchestra login bypass exploited: protect your virtual servers
A critical Xen Orchestra flaw lets attackers sign in as admin without a password and take over XCP-ng hosts. Versions to install and checks to run.
Many small businesses run their servers as virtual machines on a single host or a small cluster. If yours uses XCP-ng, it is very likely managed through Xen Orchestra, and on November 10, 2026, its developer Vates warned that a critical login flaw in Xen Orchestra is being actively exploited. Because Xen Orchestra controls every virtual machine and usually the backups too, this is one to check today, not at the next maintenance window.

What happened
Vates' advisory VSA-2026-062 describes an authentication bypass: a specially crafted cookie lets an attacker who can reach the Xen Orchestra web interface sign in with administrator rights, without a password. Vates says a compromise of Xen Orchestra can lead to code running on the managed pools and a full takeover of XCP-ng hosts as root. It affects Xen Orchestra installed from source and the Xen Orchestra Appliance (XOA).
BleepingComputer reports that Vates confirmed active exploitation and that no CVE number had been assigned at the time. One detail stands out: Vates says a successful bypass leaves no entry in the Xen Orchestra logs, so a clean log does not prove you were not attacked. CyberInsider notes that a second, separate advisory, VSA-2026-063, covers a way to compromise a host by importing a crafted virtual machine, which the same attacker abused, and that it was not yet fixed when the first patch shipped.
Which version you need
Reports differ on the version labels. Vates' own advisory says the fix is in Xen Orchestra 6.9.2 (stable channel) and 6.10.1 (latest channel), with xo-server package versions 5.211.2 and 5.213.1 respectively. The safest check is the xo-server version shown in Xen Orchestra's About page: if it is lower than those numbers, you are exposed. Installs built from source should be updated to the latest code.
What to do now
- Update Xen Orchestra first. On XOA this is the built-in updater. Confirm the xo-server version afterward.
- Take it off the internet. Vates' advice is that Xen Orchestra should never be exposed publicly and should sit on a dedicated management network. If staff or an IT provider manage it remotely, they should come in over a VPN with multifactor sign-in, not an open port.
- Limit VM import rights. Until VSA-2026-063 is fixed, Vates recommends that only the Admin user can import virtual machines, and that you disable other users holding import or network-change permissions.
- Check for signs of compromise. Vates' advisory lists attacker IP addresses to block and specific checks to run on XCP-ng hosts, including a virtual machine named "pivot2" and unexpected scheduled tasks. Your IT provider should run them. Vates warns that a clean result is not proof, because other attackers may behave differently.
- If anything is found, Vates recommends rotating every password and secret Xen Orchestra stores: host root passwords, pool secrets, user accounts, and the credentials for backup destinations such as NAS shares or cloud storage. It also recommends a full reinstall rather than cleanup.
Why the backups matter here
Xen Orchestra is often both the hypervisor console and the backup tool. An attacker with admin rights could delete backup jobs or reach the storage where backups land, which is exactly what ransomware crews look for before encrypting. Make sure at least one backup copy sits somewhere Xen Orchestra's stored credentials cannot delete, such as immutable or offline storage, and that you have tested restoring from it.
How we can help
Our disaster recovery planning service reviews where your virtual machines and their backups live and who can reach them. If virtual servers or backups have already been damaged, see our virtual machine and backup recovery page, and our managed backup service keeps an isolated copy. Call (213) 986-4855.