Xen Orchestra is the panel from which hosting providers, IT departments and a legion of homelabs govern their virtual machines. Since November 10, that panel has had an open door that asks for no password: it is enough to send a cookie with an empty JSON object for the system to return the first session token it finds and treat the visitor as its owner. Vates, the French company that develops the software, classifies the flaw as critical and confirms that someone is exploiting it right now against real installations.
The flaw is called VSA-2026-062, it does not yet have a CVE identifier or a CVSS score, and it affects Xen Orchestra and the Xen Orchestra Appliance. The authentication bypass does not stop at an administration panel: from there the attacker can execute code on the managed pools and take full control of an XCP-ng node with root privileges. In other words, the same server that hosts a client's virtual machines can end up being used to attack the others.
The uncomfortable part is not the programming error, it is the context. Exposing the management panel to the internet is a widespread habit because it is convenient for administering from home, and this flaw turns that convenience into a silent entry point. Vates warns that exploitation does not generate any identifiable entry in the application logs: anyone who wants to know whether they have been breached will have to look at the HTTP traffic, not the logs.
An empty cookie that turns into an administrator
The mechanism is so simple that it is hard to believe it worked. Xen Orchestra accepts requests to its REST API with an authentication token inside a cookie. The code that interprets that cookie converts `authenticationToken=j:%7B%7D` into an empty object, `{}`, and passes it to the token provider without requiring it to be a string. The token collection interprets that empty object as a query with no filter and returns the first one in the list; the provider authenticates the request as the owner of that token if it has not yet expired. With the session open, the `/rest/v0/users/me/authentication_tokens` route hands out reusable session identifiers.
An empty object where a string was expected is the kind of error that appears when one layer validates and another trusts that the first one validated. Here there is no sophisticated injection or exploit chain: there is a data type that travels unchecked to a function that was not written to receive it. The consequence is that the attacker inherits the privileges of the first live session it finds, and in an installation with activity that first session is usually an administrator's.
What makes the flaw serious is not the session bypass, but where it happens. That panel holds the keys to all the virtual machines and to the environment's backups.
The official Vates advisory documents the full chain and the indicators of compromise of the campaign that is exploiting it. The actor operates from `91.211.251.112:8001`, an address that VirusTotal had already flagged as a RedLine Stealer command-and-control server, and from a hidden service on Tor. The fact that the same server had previously been used to steal passwords points to an opportunistic attacker profile with recycled tools, not a group with state resources.
The trail when entry is through the hypervisor
An intrusion into a virtualization panel is different from an intrusion into a website. The attacker is not looking to deface anything: they are looking for persistence beneath the guest operating system, where the virtual machines' antivirus software cannot reach. The published indicators point to a virtual machine named `pivot2`, to configurations that redirect the serial port to a file on the host and to files named `/.ustar5`, `/.ustar6` and `/etc/cron.d/zz-ustar`. Also to tampering with `/etc/ld.so.preload`, the classic route for injecting a library into every process on the system.
The commands Vates proposes for checking a host are short, run in seconds and are worth launching before signing off on an installation, even if the panel was never exposed to the internet:
xe vm-list params=name-label,platform | grep -B1 'hvm_serial: file' zgrep -- '-serial file:' /var/log/xensource.log* ls -la /etc/ld.so.preload /.ustar* /etc/cron.d/zz-ustar*
Finding the `pivot2` machine or any of those files is not a suspicion, it is a confirmation that someone has been inside. The next step is not to clean up, it is to assume that the environment's credentials are compromised and rotate them all: those of the Xen Orchestra users, those of the proxy, those of the backups and those of the S3 buckets that are configured.
Detection at the network level adds a layer that Xen Orchestra does not offer on its own. Searching traffic captures for the strings `authenticationToken=j:%7B%7D` and `authenticationToken=j:{}` is the only direct way to see the attempt, because use of the cookie leaves no identifier in the application log. A reverse proxy with that rule configured turns an invisible failure into an alert, although it is best not to rely on it entirely: Vates warns that the rule can be bypassed with other encoding formats of the same object.
Three defenses, then: update, close the door and watch the traffic. The first covers the flaw, the second reduces the damage and the third serves to find out whether the response comes too late.
Patching is not enough if the panel faces the internet
The fixed packages are available in both channels. Xen Orchestra 6.9.1, in the stable channel, includes xo-server 5.211.2; Xen Orchestra 6.10.0, in the latest channel, carries xo-server 5.213.1. Anyone who cannot update already has three reasonable mitigations: take the instance off the internet and put it on a dedicated management network, block the attacker's address and domain to break the command chain, and block the empty token in the WAF or in the reverse proxy.
None of the three solves the underlying problem. A virtualization panel is critical infrastructure: if it is reachable over the internet, any authentication failure becomes a total compromise with no further steps required. Vates's recommendation not to expose Xen Orchestra is not a footnote; it is the measure that would have left this attack without a target.
There is also a calendar factor. This November is proving eventful for XCP-ng: the same vendor published the advisory for CVE-2026-98432, a memory flaw in the IPv4 code affecting XCP-ng 8.3, and a week later comes an exploited authentication bypass. Anyone administering these environments would do well to treat the pair of advisories as a single maintenance window rather than two separate scares.
The link nobody audits
Virtualization lives in a blind spot of everyday security. Teams review the operating system of the machines, the applications running inside them and user credentials, while the hypervisor remains there, with a web interface that everything else depends on, and it rarely makes it into the inventory of exposed assets. VSA-2026-062 is not an exotic flaw: it is proof that an empty object in the wrong place is enough to bypass one of the most sensitive layers of the infrastructure.
As long as there is no assigned CVE and no public analysis of the vector, the exposure window depends on one thing, and it is the same as always: how long it takes an update to reach the machine that matters. Vates' advisories carry a date, a version and a verification command. What is missing is the habit of running them, as the case of the QNAP NAS compromised by Plex2Shellshowed, where the backup server ended up becoming the gateway into the entire network.