Critical Vates Xen Orchestra vulnerability: #
Vates disclosed that Xen Orchestra contains a critical authentication bypass vulnerability in its REST API, tracked as VSA-2026-062 and GHSA-2r3w-c2vx-fv5g (no CVE ID has been assigned yet). REST cookie parsing turns the cookie value authenticationToken=j:%7B%7D into an empty object ({}). Instead of requiring the token ID to be a string, REST authentication passes that object to the token provider. The token collection treats the empty object as an unfiltered lookup and returns its first token, and the request is authenticated as that token's owner if the token has not expired. A remote, unauthenticated attacker can then call the authenticated /rest/v0/users/me/authentication_tokens route to retrieve reusable login tokens and perform actions with Admin privileges. Compromise of Xen Orchestra can lead to arbitrary code execution on managed pools and full takeover of XCP-ng hosts as root.
There is evidence that VSA-2026-062 is being actively exploited in the wild.
The following versions are affected
- Xen Orchestra (stable): Versions prior to 6.9.2 (xo-server prior to 5.211.2)
- Xen Orchestra (latest): Versions prior to 6.10.1 (xo-server prior to 5.213.1)
- Xen Orchestra (latest): Versions prior to 6.10.1 (xo-server prior to 5.213.1)
What is Vates Xen Orchestra? #
Xen Orchestra is the web-based management interface for XCP-ng and XenServer virtualization pools, and is included in the Xen Orchestra Appliance (XOA).
What is the impact? #
Successful exploitation of this vulnerability would allow a remote, unauthenticated attacker to bypass authentication and gain administrative control over Xen Orchestra, which could potentially result in arbitrary code execution and full root-level compromise of the managed virtualization hosts.
Are any updates or workarounds available? #
Users are encouraged to update to the latest version as quickly as possible:
- Xen Orchestra (stable): Upgrade to version 6.9.2 (xo-server 5.211.2) or later.
- Xen Orchestra (latest): Upgrade to version 6.10.1 (xo-server 5.213.1) or later.
- Xen Orchestra Appliance: Update to a release that includes Xen Orchestra 6.9.2 or 6.10.1 or later.
If Xen Orchestra was installed from source, update to the latest master.
Mitigation:
- Do not expose Xen Orchestra to the Internet; place it on a dedicated management network.
- Block requests containing authenticationToken=j:{} or authenticationToken=j:%7B%7D in a WAF or reverse proxy.
- If compromise is suspected, rotate all passwords and secrets used by Xen Orchestra and reinstall from a clean image, as cleanup alone cannot guarantee removal of backdoors.
Finding exposed Xen Orchestra services with runZero #
From the Services Inventory, use the following query to locate potentially impacted assets:
https://docs.vates.tech/security-advisories/advisories/2026/vates-sa-2026-062/