Attackers are actively exploiting a critical authentication bypass in Xen Orchestra, the web-based management platform from French vendor Vates, to gain administrative control over XCP-ng virtualization infrastructure. The flaw enables remote adversaries to take over virtualization hosts and execute arbitrary code on managed systems.
Xen Orchestra, maintained by Vates, serves as the central management interface for XCP-ng environments, handling virtual machines, hosts, and resource pools. The vulnerability, designated VSA-2026-062, affects both Xen Orchestra and the Xen Orchestra Appliance (XOA). A CVE number and CVSS rating have not yet been issued.

The flaw resides in how the platform handles authentication tokens within REST API requests. Attackers can send a specially crafted cookie containing an empty JSON object—authenticationToken=j:%7B%7D—to bypass authentication entirely. This malicious cookie tricks Xen Orchestra into retrieving an existing authentication token and logging the attacker in as that token's owner, circumventing the need for valid credentials.
After gaining access, attackers can retrieve reusable login token IDs through the /rest/v0/users/me/authentication_tokens REST API endpoint, enabling persistent access to the system.
An adversary can bypass authentication and perform actions with 'Admin' privilege. Xen Orchestra compromise can lead to arbitrary code execution on managed pools and a full XCP-ng node takeover as root.
Vates
Vates has released patched versions: Xen Orchestra 6.9.1 (stable) and 6.10.0 (latest), along with updated xo-server packages 5.211.2 and 5.213.1. The company strongly recommends immediate installation of these updates. For environments unable to patch quickly, Vates advises restricting Xen Orchestra access to isolated management networks and blocking known malicious IP addresses.
Security researchers Filip Magic and Christoffer Olsen, both from TDC NET Security, discovered and reported the vulnerability.
Indicators of Compromise and Detection Methods
Vates has confirmed active exploitation and released indicators of compromise (IOCs) to assist administrators in identifying intrusions:
- Attacker infrastructure: Connections to 91.211.251.112:8001 or ustar3rqxgnskzgnwkgpofgtvxevm6cx3lxdbwt4mndtveqyaohid.onion:3333
- Suspicious authentication cookies: HTTP requests with authenticationToken=j:%7B%7D or authenticationToken=j:{}
- Virtual machines: A VM named pivot2
- Modified VM configurations: Virtual machines set with the hvm_serial: file parameter
- Unusual files: /etc/cron.d/zz-ustar, /etc/cron.d/zz-ustar2, /.ustar5, and /.ustar6
Administrators can run the following commands on XCP-ng hosts to check for suspicious VM configurations and malicious artifacts:
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*
Vates cautions that exploitation leaves no trace in standard logs—the specially crafted cookies do not generate identifiable audit entries. Detection requires active HTTP traffic monitoring at the network level.
The company notes that these IOCs are specific to the known attack campaign and may vary across different threat actors. Organizations suspecting compromise should immediately rotate all passwords and secrets associated with their virtualization environments.