Vates has patched a critical authentication bypass in Xen Orchestra, the web console used to run XCP-ng virtualization pools, and says the flaw is already being "actively exploited by a threat actor." The advisory, VSA-2026-062, was published on November 10 alongside fixed releases for both of the product's update channels.
Why it matters: Xen Orchestra holds the keys to everything it manages. Vates says a compromise of the console can lead to arbitrary code execution on managed pools and a full takeover of XCP-ng hosts as root. No credentials are needed, and according to the advisory a successful exploit leaves no log entry, so patching alone doesn't tell you whether you were already hit.
How the bug works
Per Vates, the REST API's cookie parser turns a cookie value of authenticationToken=j:%7B%7D into an empty JavaScript object, {}. That object reaches the token provider without a check that it is a string. The token lookup treats {} as a query with no filter and returns the first stored token; if that token hasn't expired, the request is authenticated as its owner. The attacker can then list reusable login tokens through /rest/v0/users/me/authentication_tokens, giving them lasting access. WindowsForum notes that a busy installation will almost always have an unexpired token on hand.
Ostorlab, which reviewed the fix, says the patch (pull request #10748, merged November 10) adds a string check on token IDs and builds the lookup query only from validated fields. Vates says the REST API, the sign-in route and the JSON-RPC session.signIn method now all reject empty or non-string token IDs, according to Ostorlab.
The flaw was discovered by Filip Magic and Christoffer Olsen of TDC NET Security, Vates says. As of November 11 there was no CVE number and no CVSS score, and Ostorlab says the issue was not yet in CISA's Known Exploited Vulnerabilities catalog.
Affected and fixed versions
| Channel | Vulnerable | Fixed release | xo-server |
|---|---|---|---|
| Latest | Before Xen Orchestra 6.10.1 | 6.10.1 | 5.213.1 |
| Stable | Before Xen Orchestra 6.9.2 | 6.9.2 | 5.211.2 |
| From source | Older master |
Latest master |
— |
The Xen Orchestra Appliance (XOA) is also affected and updates through its normal update path. Note that some early write-ups list 6.10.0 and 6.9.1 as the fixed builds; Vates' advisory page now says 6.10.1 and 6.9.2, and the xo-server versions are the same in every account, so check that number if in doubt.
There is no count of exposed servers yet. Ostorlab points to adoption instead: the popular community Docker image ronivay/xen-orchestra has about 2.8 million pulls.
What the attackers left behind
Vates lists indicators tied to the campaign it has observed. Initial activity came from 91.211.251.112:8001 and a Tor hidden service. On compromised systems, look for:
- A VM named
pivot2in Xen Orchestra. - VMs with the
hvm_serial: fileplatform setting on XCP-ng hosts. - Files
/etc/cron.d/zz-ustar,/etc/cron.d/zz-ustar2,/.ustar5,/.ustar6, and an/etc/ld.so.preloadfile — which Cyber Press reads as signs of cron-based persistence and a userland rootkit.
Vates cautions that its checks only cover this one campaign; finding nothing does not prove a system is clean.
What to do now
- Update immediately to Xen Orchestra 6.10.1 (latest) or 6.9.2 (stable), or pull the latest
masterif you build from source. - Take it off the internet. Vates says Xen Orchestra should never be exposed publicly and should live on a dedicated management network.
- Hunt on each XCP-ng host with the commands Vates provides:
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*
- Inspect traffic, not logs: search packet captures or a TLS-terminating reverse proxy for
authenticationToken=j:%7B%7DorauthenticationToken=j:{}. - Block the campaign's infrastructure in both directions: 91.211.251.112, 193.148.56.72, 37.221.208.216, 45.66.35.11, 64.65.0.120, 64.65.62.160, 89.47.51.90 and 92.60.37.247, plus Tor traffic.
- Add a temporary WAF rule for both cookie encodings if you can't patch at once — but Vates warns that regex rules can be bypassed with other encodings.
- If you suspect compromise, rotate every secret Xen Orchestra stores: proxy and backup-remote credentials (NFS, S3, Azure, SMB), root, the pool secret, user accounts, OTP secrets and mail server passwords. If compromise is confirmed, Vates recommends a full reinstall, because cleanup may not remove every backdoor.
Vates published a second Xen Orchestra advisory the same day, VSA-2026-063, rated Important, titled "Crafted keys through XO vm.import privilege," so read that advisory too while you're updating. Expect a CVE and possibly a CISA KEV listing to follow — if your team only tracks CVE feeds, this one may not show up there yet.
Sources
- Vates — VSA-2026-062: Empty-object login token docs.vates.tech
- Ostorlab — Xen Orchestra auth bypass exploited for host takeover (VSA-2026-062) blog.ostorlab.co
- Cyber Press — Hackers exploit critical Xen Orchestra authentication bypass to take over virtualization hosts cyberpress.org
- WindowsForum — Xen Orchestra authentication bypass exploited: patch XCP-ng management servers and check for compromise windowsforum.com
- Vates — 2026 security advisories index docs.vates.tech