Broadcom has fixed CVE-2026-123890, a critical flaw (CVSS 9.8) in VMware vCenter that lets any attacker with network access bypass authentication. A China-linked group had been exploiting it since September. If your company or your provider runs vCenter 8.0, 9.0 or 9.1, update today as an emergency change and look for signs of intrusion.
The essentials
- CVE-2026-123890 has a CVSS score of 9.8 and sits in vCenter's VMware Directory Service. It needs no credentials, only network access to the server (The Hacker News).
- Broadcom fixed it on 19 November in advisory VMSA-2026-0009, which also fixes four less severe flaws (CVSS 6.7 to 8.1) in SDDC Manager and VMware Tools for Windows. Those four require an authenticated or privileged attacker.
- Fixed versions: vCenter 8.0 U3m, vSphere Foundation and Cloud Foundation 9.1.1.0200 and 9.0.2.0200, and Cloud Foundation 5.2.5 for the 5.x branch (BleepingComputer).
- There is no official workaround. Broadcom treats the update as an "emergency change" and says ESX is not affected.
- Mandiant (Google) attributes the exploitation, since early September, to Armory Castle (formerly UNC5221), a suspected espionage group linked to China (SecurityWeek).
Does this affect me if I don't run the servers myself?
If your company, your IT provider or your hosting runs virtual machines on VMware, there is most likely a vCenter behind them. It is the console that governs the whole virtual infrastructure. Whoever controls it controls the file servers, the ERP and the backups. Not managing it yourself doesn't remove the risk: it means you have to ask.
The flaw also affects products that bundle vCenter. According to Broadcom, ESX is not affected. That helps little if the attacker gets in through the console that manages it.
What did the attackers do with the flaw?
According to The Hacker News, Mandiant and GTIG saw Armory Castle use a tool called BONESAW to create an SSO administrator account, steal the directory database (LMDB) and extract the SAML signing material. With that, it forged SAML tokens and installed backdoors.
vCenter was not the way in. The attackers exploited another zero-day, in BeyondTrust Remote Support (CVE-2026-102764), and from there moved to internal Linux appliances, to vCenter and to an ESXi host. Bottom line: vCenter doesn't need to be exposed to the internet to be reached. It is enough for the attacker to get into your internal network.
Charles Carmakal, CTO at Mandiant, recommends applying the patches and also hunting for signs of compromise. The patch closes the door, but it doesn't kick out whoever is already inside.
What if I'm still on vCenter 7.0?
vCenter 7.0 left general support in October 2025. A patch is only available with an extended support contract. And according to Mandiant, BONESAW works against vCenter 7.x and 8.x. Without a patch, all you can do is reduce network exposure while you decide between migrating or paying for extended support.
What to do today
- Ask your IT lead or managed provider whether you use vCenter and which version.
- Schedule the update to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200 as an urgent change. The updates are cumulative and cannot be installed with vCenter Quick Patch. Virtual machines keep running, but management access drops briefly.
- If you plan to move to VMware Cloud Foundation 9.1.1, be careful: installing 8.0 U3m or 9.0.2.0200 blocks that later upgrade (the "Back-in-Time" issue). Upgrade to 9.1.1 first or wait for VCF 9.1.2.
- If you are on 7.0 or earlier, isolate vCenter from the internet and from the user network, and restrict access to administration IPs.
- Look for signs: SSO or local administrator accounts you don't recognise, SSH enabled on vCenter without anyone asking for it, and unusual access on port 2012.
- Check whether you use BeyondTrust Remote Support, the entry point of this campaign.
- Make sure your backups are disconnected from vCenter.
What it means for an SME
vCenter concentrates too much power in a single point. If it falls, everything falls, including the backups that should save you. So the priority is not just patching, but making sure your backups don't depend on that console.
This is the second critical authentication flaw in the VMware Directory Service this year. The previous one, CVE-2026-59309, was patched on 29 July. Two emergencies in four months in the same component show that you need a process to apply critical patches within days, not at the next quarterly maintenance window. And if a provider manages your vCenter, that timeframe should be in the contract.
With no official workaround there is no shortcut: either you update or you cut network access. And since exploitation started in September, don't assume a vCenter is clean just because it is now patched. If you need help reviewing exposure or hunting for signs of compromise, see how we work in cybersecurity.
Frequently asked questions
Is updating vCenter enough?
No. The flaw has been exploited since September, so besides updating you need to check for unknown SSO accounts, SSH enabled for no reason and odd access on port 2012.
Do I have to stop the virtual machines to update?
No. Virtual machines keep running. Only vCenter management access drops briefly.
Do I have to report it if I find signs of compromise?
If personal data is involved, GDPR requires notification within 72 hours. If you are an essential or important entity, NIS2 obligations also apply.
Sources
- BleepingComputer – VMware patches vCenter zero-day exploited in attacks since September
- SecurityWeek – Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT
- The Hacker News – Critical VMware vCenter Zero-Day Flaw Lets Network Attackers Bypass Authentication
- The Hacker News – China-Linked Hackers Exploit Critical VMware vCenter Zero-Day to Gain Admin Access and Steal Data