Server room racks with a warning on screen showing an authentication bypass vulnerability in a virtualisation console

Vates has confirmed that attackers are already exploiting VSA-2026-062, a critical authentication bypass vulnerability in Xen Orchestra, as reported by BleepingComputer and The Hacker News. The flaw sits in the tool many teams use to manage their virtual machines. So if you run Xen or XCP-ng, this one deserves your attention today.

This post explains what happened in plain language. It also lists what to do this week, in a sensible order.

What this authentication bypass vulnerability allows

Xen Orchestra is the management console for Xen-based virtualisation. Think of it as the control room for your servers. An authentication bypass means an attacker gets in without proving who they are, so the login screen stops protecting anything.

According to BleepingComputer, a successful bypass grants Admin-level access. That access can lead to code execution on managed pools. It can also lead to root takeover of XCP-ng nodes. In other words, the attacker does not just look at your servers, because they can run commands on them.

Vates has confirmed the exploitation, and both outlets report that it is happening now. So this is not a theoretical risk that waits for a proof of concept to appear.

Why the management layer matters more than one server

Indian MSPs, hosting firms and mid-size companies often run Xen-based virtualisation. Some leave the management console reachable from the internet because it makes remote work easy. That convenience has a cost, since admin access to the management layer can put every hosted virtual machine at risk.

Consider a hosting provider with dozens of customer workloads on a few pools. One compromised console can touch all of them. For a regulated business, that can also raise reporting questions with CERT-In, so it is better to close the door early.

What to do this week

Start with the three steps below. They work in this order because each one reduces risk in a different way.

  • Update Xen Orchestra to the fixed version listed in the Vates advisory.
  • Take the management interface off the public internet and move it to a dedicated management network.
  • Review admin logins and VM import activity for unfamiliar access.

The update comes first because it closes the flaw itself. The network change comes second because it limits the damage from the next bug. Vates recommends not exposing Xen Orchestra to the internet and keeping it on a dedicated management network.

If you find admin sessions you cannot explain, treat the host as compromised. Then rotate the credentials, keys and tokens that the console held. The same quick-patching habit applies to browsers, as we saw with patching a Chrome zero-day.

How to confirm your fix actually worked

After patching, check from outside your network that the console no longer answers. Do not rely on the firewall rule alone, because rules drift over time. A quick external test shows what an attacker would see.

It also helps to understand vulnerability assessment and penetration testing. A scan lists known weaknesses, while a penetration test tries to break in the way an attacker would. Login flaws are the kind of problem a skilled tester checks by hand.

If nobody reads your logs overnight, it is worth reading our guide on MDR, SOC and SIEM. It explains which kind of monitoring fits a team of your size.

A flaw like this is a good reminder that the management layer deserves the same care as the servers it controls. Patch it, hide it from the internet, and check who has been logging in.

Frequently asked questions

What is an authentication bypass vulnerability?

An authentication bypass vulnerability is a software flaw that lets someone reach protected features without valid credentials. The login check fails, is skipped or can be tricked. As a result, an attacker may act as a legitimate user, or even an administrator, without ever knowing a password.

How do attackers bypass authentication?

Common routes include flaws in login logic, weak or default passwords, stolen session tokens and unprotected admin pages. The attacker looks for any path that skips the normal identity check. Strong passwords alone do not help if the software itself fails to enforce the check, so patching matters as much.

Can penetration testing find authentication bypass flaws?

Yes, in many cases. Testers try to reach protected pages without logging in, reuse sessions and tamper with requests. However, a test finds only what exists at that time, so a brand new flaw in third-party software can still appear later. That is why regular patching and testing work best together.

How can you prevent authentication bypass vulnerabilities?

Keep software updated, keep admin consoles off the public internet and require multi-factor authentication where the product supports it. Also log and review admin logins. No single step is enough, so layer them. For tools like Xen Orchestra, Vates recommends a dedicated management network.

Join the discussion

Is your virtualisation management console reachable from the public internet today, and who on your team would know if it were?

Ask Selkey

If you want a second pair of eyes on your own security, the Selkey Cyber Security Pvt Ltd team is happy to talk. You can call +91 7490 999 564 or +91 7777 999 564, email hello@selkeycybersecurity.com or visit www.selkeycybersecurity.com.

Sources