On 10 November 2026, the French vendor Vates published a bulletin rated critical, VSA-2026-062, about a Xen Orchestra flaw already being used by an attacker. A simple malformed cookie is enough to impersonate a legitimate user, potentially an administrator, and then take over the XCP-ng virtualisation hosts managed by the tool. Versions 6.9.2 and 6.10.1 fix this authentication bypass, but a second flaw used in the same attack chain remained unpatched at the time of publication.
An empty cookie that opens the administration door
Xen Orchestra is the web console used to administer XCP-ng pools, the virtualisation platform developed by Vates, which The Hacker News describes as a French company. According to the Vates bulletin, the flaw lies in how the REST API reads cookies. When the authenticationToken cookie contains the value j:{}, or its encoded form j:%7B%7D, the tool converts it into an empty JSON object instead of a character string. This object is then passed to the token provider without any type check.
What follows is mechanical: in the absence of any criterion, the lookup returns the first token stored in the database. As long as that token remains valid, the intruder inherits its owner’s rights. As IT-Connect explains, an API route then makes it possible to list reusable token identifiers, giving the intruder persistent access. Vates sums up the stakes bluntly: administrative rights, code execution on the managed pools and, ultimately, full control of an XCP-ng node with root rights.
Confirmed exploitation, and a second flaw without a fix
The vendor states that a malicious actor is actively exploiting the flaw. Its bulletin cites a point of contact on port 8001 of an IP address and a Tor hidden service, and lists a total of eight addresses to block. According to The Hacker News, the VirusTotal platform links the first of these addresses to a command server of the RedLine information stealer. The outlet also notes that it is unknown how long the attack has been circulating and whether it was first used as a vulnerability unknown to the vendor.
On the same day, Vates published a second bulletin, VSA-2026-063, rated “important”. When a virtual machine is imported, Xen Orchestra relays the file to the host without inspecting it, which makes it possible to slip in malicious parameters, notably hvm_serial. According to IT-Connect, the attacker combined the two flaws: first obtaining administrative rights through the empty cookie, then importing a tampered machine. This second flaw affects Xen Orchestra up to and including version 6.10.1 and had no fix as of the bulletin’s date. The Hacker News reports that a fix was in preparation. As of 17 November 2026, this bulletin still had not been updated since 10 November: its status remained “in progress”, with Vates saying it was actively working on a fix, without announcing a date.
A word of caution on version numbers: The Hacker News mentions fixed versions 6.9.1 and 6.10.0, whereas the Vates bulletin, which is authoritative, gives 6.9.2 for the stable channel and 6.10.1 for the latest channel. On the package side, xo-server 5.211.2 or 5.213.1 is required. Installations from source must follow the latest main branch.
Steps to take immediately
For teams running XCP-ng, the list of priorities follows from the bulletin:
- Update the XOA appliance or the Xen Orchestra installation to 6.9.2 or 6.10.1.
- Take the console off the Internet: Vates recommends placing it on a dedicated administration network.
- Filter the eight listed IP addresses and Tor traffic to the hidden service.
- If an immediate update is not possible, block both forms of the cookie on a web application firewall or reverse proxy, bearing in mind that the vendor warns that a regular-expression rule can be bypassed.
- Restrict virtual machine imports to administrators, by disabling accounts that hold the import or network-creation privileges listed by Vates, pending the fix for VSA-2026-063.
Looking for traces of an intrusion
The difficulty is that unauthenticated access leaves no usable trace in the logs, according to IT-Connect. The effects of the intrusion must therefore be sought instead. Vates lists several: a virtual machine named pivot2, machines whose serial port is redirected to a file (hvm_serial: file parameter), as well as several files on the hosts, including /etc/cron.d/zz-ustar, /etc/cron.d/zz-ustar2, /.ustar5, /.ustar6 and /etc/ld.so.preload. HTTP requests containing the empty cookie, if an upstream device has retained them, are another clue.
The vendor insists: finding nothing does not prove the absence of compromise. In case of doubt, it advises renewing all secrets, from root passwords to the pool secret, including access to remote backups and proxies, two-factor authentication codes and the email configuration. If the intrusion is confirmed, Vates recommends a complete reinstallation. The discovery is credited to Filip Magic and Christoffer Olsen of the TDC NET Security team.
Beyond this case, the episode is a reminder of an often-neglected rule: a virtualisation console holds the keys to the entire estate. Exposing it directly on the Internet amounts to offering attackers a single entry point to all servers, and neither the absence of a CVE identifier nor of a severity score should delay the update.
Frequently asked questions
Which versions of Xen Orchestra are vulnerable to VSA-2026-062?
According to Vates, all versions prior to 6.9.2 on the stable channel and to 6.10.1 on the latest channel, as well as any XOA appliance that has not been updated. The fixed packages are xo-server 5.211.2 and 5.213.1.
Does the flaw have a CVE identifier?
Not to date: as of 17 November 2026, the Vates bulletin still mentioned neither a CVE identifier nor a CVSS score, but it rates the flaw as critical and confirms its active exploitation. This absence is no reason to wait before patching.
Is updating enough to be protected?
It closes the authentication bypass, but not the VSA-2026-063 import flaw, still unpatched as of 17 November 2026. Virtual machine imports must therefore also be reserved for administrators, the console taken off the Internet and the indicators of compromise listed by the vendor searched for.
Sources
- VSA-2026-062: Empty-object login token — Vates (vendor advisory), 2026-11-10
- Xen Orchestra : cette faille critique déjà exploitée permet de compromettre les hôtes XCP-ng — IT-Connect, 2026-11-12
- Hackers exploit critical Xen Orchestra flaw — The Hacker News, 2026-11-10
- VSA-2026-063: Crafted keys through XO vm.import privilege — Vates (vendor advisory), 2026-11-10