Xen Orchestra: actively exploited authentication bypass via empty-object token lookup on the REST interface
Identifiers: VSA-2026-062
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
Vates advisory VSA-2026-062, published and updated 10 November 2026 and rated critical, describes an authentication bypass in the Xen Orchestra REST interface. A malformed empty-object lookup is not filtered, so it returns the first token in the store; if that token is unexpired, the request is accepted and the unauthenticated requester acts as that token's user. Vates states the flaw is being actively exploited. The reviewed vendor advisory does not name a CVE as of this check. Xen Orchestra before 6.9.2 (stable) and 6.10.1 (latest) is affected, including the Xen Orchestra Appliance. Fixed releases are 6.9.2 stable and 6.10.1 latest, with xo-server 5.211.2 stable and 5.213.1 latest. Source installs should move to the current patched master per vendor guidance; the fix is tracked in pull request 10748.
Impact
If the first returned token belongs to an administrator, the attacker gains admin on Xen Orchestra and may reach root on hosts in managed pools. This outcome is possible but not automatic. Vates warns that unauthenticated access may leave no log entry, so the absence of indicators does not prove an instance is clean.
Who is affected
Xen Orchestra or XOA instances running an affected, unpatched build (before 6.9.2 stable or 6.10.1 latest, or a source build predating the fix), whose REST interface an attacker can reach, and where the first token returned by the unfiltered lookup is unexpired. Patched builds are not affected. Internet-exposed instances carry the highest risk; VPN-only reachability is not automatically safe.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Xen Orchestra / Xen Orchestra Appliance | Before 6.9.2 (stable) / 6.10.1 (latest), per vendor channel | 6.9.2 stable / 6.10.1 latest; xo-server 5.211.2 stable / 5.213.1 latest |
Exploitation evidence
Exploitation reported. Vates reports active exploitation in VSA-2026-062; the start time is not known and unauthenticated access may not be logged.
Actions
- Update through your channel to 6.9.2 stable or 6.10.1 latest; from source, pull the current patched master.
- Verify the running xo-server version is 5.211.2 (stable) or 5.213.1 (latest) or newer.
- Move Xen Orchestra off the public internet onto a dedicated management network, as the vendor recommends.
- Do not treat WAF cookie-pattern rules or blocking known IPs as remediation; the vendor notes the pattern rule can be bypassed.
- If compromise is confirmed, follow the vendor's advice: full reinstall and rotation of every secret Xen Orchestra held, including backup remotes, pool root credentials, OTP and mail configuration. Patching does not remove backdoors.
- Validate backups before restoring and avoid blindly restoring a possibly compromised configuration.
- Use the vendor advisory for qualified investigation guidance.
Unknowns
- The reviewed vendor advisory does not name a CVE as of 11 November 2026.
- When exploitation began is not known.
- Whether a given instance was accessed cannot be determined from logs alone.
Sources
- Vates VMS https://docs.vates.tech/security-advisories/advisories/2026/vates-sa-2026-062/
- Xen Orchestra project https://github.com/vatesfr/xen-orchestra/pull/10748
Change history
- — Published: 11 November 2026: ViWeb published this briefing based on Vates advisory VSA-2026-062 (critical), which was published and updated 10 November 2026 for Xen Orchestra, states active exploitation and lists fixed releases 6.9.2 stable and 6.10.1 latest, xo-server 5.211.2 stable and 5.213.1 latest; the reviewed advisory does not name a CVE.