Xen Orchestra Authentication Bypass Is Exploited: Fixed Versions, Signs of Compromise and an Unpatched Second Flaw

Published:

Vates, the company behind Xen Orchestra and XCP-ng, says a critical authentication bypass in Xen Orchestra is being actively exploited. The flaw, tracked as VSA-2026-062 and published on November 10, 2026, lets an attacker act as an administrator without credentials and can lead to root access on the XCP-ng hosts the tool manages. A fix is out. A second flaw that attackers are chaining with it, VSA-2026-063, had no fix when Vates last updated its advisory. This post follows Vates’ own advisories as read on November 13.

What is VSA-2026-062?

Vates’ advisory is titled “Empty-object login token” and rated Critical, with no CVE number or CVSS 4.0 score yet. It covers Xen Orchestra and the Xen Orchestra Appliance. According to Vates, the REST layer parses a cookie containing an empty object and passes it to the token provider without checking its type. The token lookup then returns the first stored token, and the request is authenticated as that token’s owner if the token has not expired. From there an attacker can list reusable login token IDs and act with admin privileges, which can mean code execution on managed pools and root-level takeover of XCP-ng nodes.

Vates credits Filip Magic and Christoffer Olsen of TDC NET Security. CyberInsider reports that Vates confirmed a threat actor is exploiting it. We have no information on when exploitation began or how many installations were hit.

Which versions are fixed?

Earlier coverage gave conflicting numbers. The advisory as it reads now is consistent:

  • Affected: Xen Orchestra before 6.9.2 (stable) and before 6.10.1 (latest), plus the Xen Orchestra Appliance.
  • Fixed: Xen Orchestra 6.9.2 on the stable channel and 6.10.1 on the latest channel. The fixed xo-server packages are 5.211.2 (stable) and 5.213.1 (latest).
  • Source installs: update to the latest master.

Some outlets, and an earlier reading of the advisory’s mitigation list, gave 6.9.1 and 6.10.0 as the fixed releases, so if you applied those, check that you are on 6.9.2 or 6.10.1 or later. CyberInsider advises checking the installed xo-server package against the current advisory rather than relying on the Xen Orchestra version label. The fix is described in Xen Orchestra pull request 10748 on GitHub.

The second flaw: VSA-2026-063

Vates’ VSA-2026-063 is rated Important and covers crafted keys in a VM import. Users with the vm.import, sr/import:vm, network/action:create or network/action:update privileges can import a raw XVA file that sets fields Xen Orchestra does not check, which Vates says could let an unprivileged user compromise an XCP-ng host. The advisory says a threat actor has already used this path with admin privileges obtained through VSA-2026-062.

It affects Xen Orchestra 6.10.1 and earlier. As of the advisory’s November 10 update, the status is “In progress” and no fix is in the latest or stable channels. Patching VSA-2026-062 does not close it. Vates’ mitigation is to disable every user who holds those four privileges so that only admins can import VMs.

How to check for compromise

Vates says a successful exploit leaves no Xen Orchestra log entry for the unauthenticated access, and that missing indicators do not prove a system is clean. The listed indicators cover only this campaign.

  • Web traffic: requests containing authenticationToken=j:{} or authenticationToken=j:%7B%7D. Vates warns other encodings may slip past a rule that only matches these.
  • Xen Orchestra: a running VM named pivot2.
  • XCP-ng hosts: VMs with the hvm_serial: file parameter (list them with xe vm-list params=name-label,platform), pivot2 references in rotated /var/log/xensource.log* files, and the files /etc/cron.d/zz-ustar, /etc/cron.d/zz-ustar2, /.ustar5, /.ustar6 and /etc/ld.so.preload.
  • Network: Vates lists eight command-and-control IP addresses to block in both directions (starting 91.211.251[.]112 and 193.148.56[.]72) and a Tor onion service. Use the full list on the advisory page.

What to do now

  1. Update Xen Orchestra and the Appliance to 6.9.2 or 6.10.1 (or later), or rebuild a source install from the latest master.
  2. Remove internet exposure. Vates says to keep Xen Orchestra on a dedicated management network.
  3. Restrict VM import to admins to reduce the VSA-2026-063 risk until Vates ships a fix.
  4. Block the listed addresses and add a WAF or reverse-proxy rule for the empty-token cookie as a stopgap only.
  5. If you find signs of compromise, rotate every secret the platform uses, including proxy, backup remote, root, pool secret, user, OTP and mail server credentials. Vates advises a full reinstall after a confirmed compromise because cleanup may not remove every backdoor.

As of the CISA Known Exploited Vulnerabilities catalog version 2026.11.10, which we checked on November 13, neither flaw is listed, and neither has a CVE. That can change quickly, and Vates may revise either advisory, so read the originals before acting. For a similar patch-now case, see our post on the WordPress 7.1.4 flaw CISA says is exploited.

Sources

Image: “DE-CIX GERMANY – Switch Rack” by Stefan Funke, CC BY-SA 2.0, via Wikimedia Commons.

Like our coverage? Add stepphase.com as a preferred source on Google to see more of our stories in Top Stories.

Saif Ali Tai
Saif Ali Taihttps://xplorely.com/
I'm Saif Ali Tai, a tech blogger and software engineer with 8+ years of experience building apps, and I run StepPhase as its editor. I cover technology news, AI tools and security stories that matter to everyday users. Articles here are drafted with AI assistance and checked against the sources linked in each post.

Related articles

Recent articles