VulnerabilitiesZero Trust

Xen Orchestra Auth Bypass Is Being Exploited. The Hypervisor Console Is the Keys to Everything.

November 12, 2026 · Brian Deitch

If you run XCP-ng and manage it with Xen Orchestra, stop reading here, go check your version, and come back. I'll wait.

Vates, the company behind both, is warning that two critical flaws in Xen Orchestra are being exploited in attacks. One gets an unauthenticated attacker admin. The other lets an admin compromise the hypervisor hosts underneath. Chained together, Vates says that can mean "arbitrary code execution on managed pools and a full XCP-ng node takeover as root."

That's not one VM. That's every VM on the pool.

What We Know

Per Vates' advisories, as reported by SecurityWeek on November 11:

  • Flaw 1, authentication bypass (VATES-SA-2026-062): a bug in Xen Orchestra's REST authentication. A malformed token gets turned into an empty lookup, which returns the first stored token. If that token hasn't expired, you're now logged in as whoever owns it. Unauthenticated attacker, administrator privileges.
  • Flaw 2, malicious VM import (VATES-SA-2026-063): lets an attacker with admin rights import a crafted VM that can compromise XCP-ng hosts. Vates says a fix for this one is still being developed.
  • Affected: Xen Orchestra releases before 6.9.2 (stable) and 6.10.1 (latest), plus the Xen Orchestra Appliance.
  • No CVEs yet, and no CVSS score published. Vates calls them critical.
  • Exploitation: the same actor is using both, operating initially from 91.211.251.112:8001 and over Tor.
  • The uncomfortable part: Vates says the unauthorized access "is not logged," and that not finding its IoCs "is not sufficient to conclude that no compromise has occurred."

What we don't know: how many instances are exposed, who's behind it, or how many victims there are. Vates hasn't said, and I'm not going to guess.

Why This Is a Big Deal

Virtualization management consoles are the quiet crown jewels. Ransomware crews love them because one login lets you encrypt or wipe an entire datacenter's worth of VMs at the hypervisor layer, under every endpoint agent you've deployed. We've watched this play out with other hypervisor platforms for years.

And here the front door doesn't even require a password, and the break-in doesn't leave a log. That combination is about as bad as it gets for incident response.

Credit to Vates for publishing the advisories, IoCs and concrete mitigations quickly, and for being blunt that missing IoCs doesn't mean you're clean. That honesty is more useful than a reassuring paragraph.

The Architecture Point

I work at Zscaler, so factor that in. But the question I'd ask isn't "is my Xen Orchestra patched," it's "why could an attacker on the internet or Tor reach it at all?" A hypervisor console should be reachable by a handful of named admins on managed devices, and by nobody else. If it isn't on the internet, an auth bypass becomes an insider problem instead of a Tuesday.

Every vendor ships bugs, Zscaler included. Management planes are where those bugs hurt the most, so they're where exposure should be the smallest.

What To Do

  • Upgrade Xen Orchestra to 6.9.2 (stable) or 6.10.1 (latest) or later, including the appliance.
  • Get it off the internet. Vates recommends putting Xen Orchestra behind a dedicated network. Do that today, not after the second fix lands.
  • Block the empty token with a WAF rule, as Vates suggests, until you've patched.
  • Block the IoCs Vates published, including 91.211.251.112, and consider blocking Tor to management interfaces entirely.
  • Rotate credentials that Xen Orchestra holds or that admins used with it.
  • If you find a compromise, reinstall. Vates says "cleanup alone cannot guarantee the removal of all backdoors." Believe them.
  • Watch for the VM import fix and apply it when it ships. Until then, restrict who can import VMs.

Bottom Line

An unauthenticated, unlogged path to admin on your hypervisor manager is being used right now. Patch it, hide it, and if there's any doubt, rebuild it. The console that controls every VM should be the hardest thing on your network to reach.

Sources: SecurityWeek, Vates VATES-SA-2026-062, Vates VATES-SA-2026-063

xen-orchestraxcp-ngvatesvirtualizationauthentication-bypassmanagement-planezero-daytor
All postsDiscuss on LinkedIn