Xen Orchestra authentication bypass VSA-2026-062 is actively exploited, Vates says
TLDR
- Vates says a critical Xen Orchestra authentication bypass, VSA-2026-062, is being actively exploited and gives attackers Admin privileges.1
- A second flaw, VSA-2026-063 in VM import, was abused by the same attacker and was unfixed on 10 November.78
- Vates lists no fixed release for VSA-2026-063, which has no CVE or CVSS score yet.8
Vates has published advisory VSA-2026-062, "Empty-object login token", dated 10 November 2026.1 It classifies the impact as Critical and says the vulnerability is actively exploited by a threat actor.1 The advisory covers Xen Orchestra and the Xen Orchestra Appliance.1 BleepingComputer describes Xen Orchestra as a web-based platform developed by Vates for managing XCP-ng virtualisation environments, including virtual machines, hosts and pools.2 The advisory lists CVSS 4.0 as "Not available yet" and no CVE, and both BleepingComputer and The Hacker News say no CVE identifier has been assigned.123
The flaw is in how Xen Orchestra handles the REST authentication cookie. Vates says REST cookie parsing turns authenticationToken=j:%7B%7D into an empty object, which REST authentication passes to the token provider without requiring a string.1 The token collection treats the empty object as an unfiltered lookup and returns its first token, and the provider authenticates the requester as that token's owner if the token has not expired.1 No credentials are needed: Vates says an adversary can bypass authentication and act with Admin privilege, and BleepingComputer says remote attackers with network access to the management interface can do so.12 An authenticated route, /rest/v0/users/me/authentication_tokens, then returns reusable login token IDs.1 Vates says a compromised Xen Orchestra can lead to arbitrary code execution on managed pools and a full takeover of XCP-ng nodes as root.1 The fix in the public pull request, #10748, rejects authentication token IDs that are not strings or are empty before the token collection is queried.5
Vates says the threat actor was operating initially from 91.211.251.112:8001 and a Tor onion service on port 3333.1 The Hacker News says VirusTotal has flagged that IP address as a RedLine Stealer command-and-control server, and that it is unclear when the activity started or whether the flaw was exploited as a zero-day.3 Vates says a successful exploit leaves no log entry, so detection depends on watching HTTP traffic for the two cookie patterns, plus checks for a running VM named pivot2 and, on XCP-ng hosts, VMs using the hvm_serial: file parameter and files such as /etc/cron.d/zz-ustar.1 It adds that these indicators cover only this campaign and that missing indicators do not prove a system is clean.1 Its mitigations are to update promptly, keep Xen Orchestra off the Internet on a dedicated management network, block the listed addresses and Tor traffic, and add a WAF or reverse-proxy rule for the cookie, while warning that regex rules can be bypassed with other encodings.1 If Xen Orchestra was compromised, it says to rotate all platform secrets, and after a confirmed compromise to reinstall fully because cleanup alone may leave backdoors.1 XCP-ng, in an update bulletin for its 8.3 LTS release, also warns that a critical Xen Orchestra vulnerability is being actively exploited and says instances reachable from the Internet should be updated immediately.4 Filip Magic and Christoffer Olsen of TDC NET Security are credited with the discovery.1
The Vates advisory says Xen Orchestra before 6.9.2 (stable) and 6.10.1 (latest) is affected and that those two releases contain the fix, with xo-server 5.211.2 on the stable channel and 5.213.1 on the latest channel.1 BleepingComputer and The Hacker News instead say the fix is in Xen Orchestra 6.9.1 (stable) and 6.10.0 (latest), with the same xo-server packages.23 The Xen Orchestra changelog lists 6.10.0, dated 29 October 2026, with xo-server 5.213.0, and 6.9.1, dated 5 October 2026, with xo-server 5.211.1.6 The advisory gives its publication date as 10 November 2026 without a time, and its page shows a last-updated time of 18:25 UTC that day.1
Update, 12 November 2026: Vates has a second Xen Orchestra advisory, VSA-2026-063, "Crafted keys through XO vm.import privilege". SecurityWeek, citing Vates, reports that the same threat actor has been exploiting the VSA-2026-062 authentication bypass and a zero-day that allows malicious VM imports that could compromise XCP-ng hosts, and that a fix is still being developed.7 The advisory is rated Important, dated 10 November 2026, with CVSS 4.0 "Not available yet" and no CVE listed.8 It names Xen Orchestra, "6.10.1 and before", and the Xen Orchestra Appliance as affected, shows its status as "In progress", and says that as of 10 November neither the latest nor the stable channel has a fix.8 SecurityWeek also says no CVE identifier has been assigned to the defects.7
Vates says Xen Orchestra talks to XAPI as pool-admin and passes the imported stream along without reading or changing ova.xml.8 A user holding vm.import, sr/import:vm, network/action:create or network/action:update can import a raw XVA with crafted keys, such as VBD.other_config:backend-local, VM.other-config:is_system_domain and VM.platform:hvm_serial.8 The advisory says other fields, including VM.other_config, VM.platform, VM.ha_restart_priority and VM.appliance, could also be manipulated, and that a malicious VM could lead to compromise of an XCP-ng host.8 It says a threat actor has abused this path, initially with Admin privilege, with a reference to VSA-2026-062, and lists the same 91.211.251.112:8001 address and Tor onion service on port 3333 as where the actor operated.8 Matthias Fetzer is credited for logs and forensic reports.8
SecurityWeek describes the zero-day as requiring administrator privileges, while the advisory says a user holding any of the four listed privileges can import the crafted XVA and that the observed abuse started with Admin privilege.78 Vates's only listed mitigation is to restrict VM import to the Admin user by disabling every user who has been given those four privileges.8
Why it matters: Vates says a bypassed Xen Orchestra can lead to root control of XCP-ng nodes, and for the separate VM import flaw it lists no fixed release, only a restriction of import privileges to the Admin user.18
Sources
- VSA-2026-062: Empty-object login token (Vates)
- Critical Xen Orchestra auth bypass flaw exploited to hijack VM servers (BleepingComputer)
- Hackers Exploit Critical Xen Orchestra Auth Bypass Flaw to Gain Admin Access (The Hacker News)
- November 2026 Security Updates (XCP-ng)
- fix(xo-server): validate authentication token IDs (PR #10748) (GitHub (vatesfr/xen-orchestra))
- Xen Orchestra ChangeLog (GitHub (vatesfr/xen-orchestra))
- Critical Xen Orchestra Flaws Exploited in Attacks (SecurityWeek)
- VSA-2026-063: Crafted keys through XO vm.import privilege (Vates)