An Empty Cookie to Host Root: Xen Orchestra's Exploited Auth Bypass (VSA-2026-062)
A single malformed cookie that parses to an empty object hands an attacker admin on Xen Orchestra, the management plane for XCP-ng virtualization, and from there, code execution on pools and root on the hosts. It's being exploited, and it leaves no log entry. Here's the flaw, the fix, and how to hunt when the logs are silent.
Executive summary. VSA-2026-062 is a critical, actively exploited authentication bypass in Xen Orchestra (XO) and the Xen Orchestra Appliance (XOA), the web management plane for XCP-ng virtualization. XO's REST cookie parsing turns the value authenticationToken=j:%7B%7D into an empty JavaScript object and trusts it, so an unauthenticated attacker gains admin on the management console. From there, admin leads to code execution on managed pools and root takeover of XCP-ng hosts, the entire hypervisor layer. Critically, Vates warns that successful exploitation leaves no log entry, and ties observed activity to a specific IP and a Tor service. Fixes are XO 6.9.2 (stable) / 6.10.1 (latest). A related issue, VSA-2026-063 (VM import permissions), can be chained. Patch immediately, take XO off the internet, and assume silent compromise if you were exposed.
What it is
| Field | Detail |
|---|---|
| Advisory | VSA-2026-062 |
| Product | Xen Orchestra / XOA (management for XCP-ng) |
| Type | Authentication bypass → admin → host root |
| Trigger | Cookie authenticationToken=j:%7B%7D parsed as {} and trusted |
| Nasty detail | No log entry on successful exploitation |
| Status | Actively exploited (activity tied to 91.211.251.112:8001 and a Tor onion) |
| Fixed | XO 6.9.2 (stable) / 6.10.1 (latest); related VSA-2026-063 |
The bug in one line
authenticationToken=j:%7B%7D → decoded → {} → "valid session"The j: prefix tells XO's cookie parser to treat the value as JSON; %7B%7D is the URL-encoding of {}. XO decodes it to an empty object and proceeds as if an authenticated session exists. No password, no token, no user, just an empty object the server mistook for a logged-in session.
Why this is a worst-case target
Xen Orchestra sits above your VMs: it manages pools of XCP-ng hypervisors. Admin on XO is admin over the virtualization layer, which means:
- Code execution on managed pools and root on the XCP-ng hosts.
- Control of every VM those hosts run: snapshot, clone, export, destroy.
- A path to data in any guest, and to backups XO manages.
Compromising the hypervisor management plane is close to game over for an environment, which is why virtualization consoles (vCenter, Proxmox, XO) are prime targets, echoing this month's other edge/management-plane compromises.
The silent-exploitation problem
Vates states that successful exploitation writes no log entry. That turns incident response upside down: you can't confirm you weren't hit by reading the XO logs, because a successful bypass looks like nothing. So for any internet-exposed or broadly-reachable XO, the safe assumption if you were exposed before patching is possible silent compromise, and you hunt at the host and VM layer, not just in XO.
Remediation
Now
- Upgrade Xen Orchestra to 6.9.2 (stable) or 6.10.1 (latest); update the
xo-serverpackages accordingly. Address VSA-2026-063 per Vates' guidance (restrict VM-import permissions where a full fix lags). - Take XO off the internet. Put the management console behind a VPN / allow-list; it should never be publicly reachable.
- Block/alert on the published indicators (the attacker IP and Tor activity) at your perimeter.
If you were exposed
- Assume silent compromise. Rotate XO, host, and any secrets XO holds (backup credentials, pool passwords, API tokens).
- Hunt at the host/VM layer (see below), since XO's own logs won't show the bypass.
Detection and hunting (when the console is silent)
| Where | Look for |
|---|---|
| XCP-ng dom0 / host | New processes, cron jobs, systemd units, SSH keys; shells spawned by management services |
| VM lifecycle | Unexpected snapshots, exports, clones or new VMs created around the exposure window |
| Network | Connections from XO/hosts to 91.211.251.112 or Tor; new outbound connections from dom0 |
| Backups | Access to or export of backup repositories XO manages |
| XO config | New admin users, API tokens, or changed settings |
Conclusion
VSA-2026-062 is a trivially-triggered auth bypass on a system that controls an entire virtualization estate, and it hides its tracks. The combination, pre-auth, hypervisor-plane impact, and no logs, makes it a patch-today, hunt-anyway event. Update XO, get it off the internet, and if you were exposed, investigate at the host and VM layer rather than trusting a silent console.
Do this now: upgrade Xen Orchestra to 6.9.2 / 6.10.1, remove any internet exposure, block the published indicators, and, if you were exposed, hunt dom0 and VM activity and rotate secrets.
Related: our network pentesting manual and The Collapsing Patch Window.
Sources: BleepingComputer, The Hacker News, SecurityOnline, Rescana, Brandefense. Fixed versions vary across early reports; confirm against Vates' advisory VSA-2026-062.
Related research
Administrator Without a Password: The VMware vCenter Auth Bypass a Chinese APT Rode for Months
A flaw in vCenter's identity layer lets anyone with network access become Administrator without a password, and Google's Mandiant says a China-nexus group quietly exploited it as a zero-day since September to deploy backdoors. Broadcom's emergency patch is out. Here's the chain, who's exposed, and how to hunt.
Your Backup Is the Target: Synology NAS RCE (CVE-2024-10441) Now Exploited by Ransomware
A critical unauthenticated RCE in Synology's DiskStation Manager, patched back in 2024, is being exploited now against internet-exposed NAS devices by a ransomware crew, and it has landed in CISA's exploited-vulnerabilities catalog. The device holding your backups is the one getting encrypted. Here's the fix.
Chrome's Eighth Zero-Day of 2026: CVE-2026-125350, a Use-After-Free in XML
A single malicious web page can corrupt memory in Chrome's XML engine and run code inside the sandbox, and Google says it's already being exploited. It's the eighth Chrome zero-day of the year. Here's the bug, the fix, why an un-relaunched browser stays vulnerable, and how to roll it out across a fleet.