If your business runs its own servers on VMware, or your IT provider or hosting company runs them for you, this one needs attention today. On 19 November 2026 Broadcom released an emergency update for VMware vCenter Server to fix a critical flaw that lets an attacker take over the management console without a password. Researchers say it had already been used in real attacks for more than two months before the fix arrived.
What happened
vCenter is the central console used to run VMware vSphere: it controls the physical hosts and every virtual machine on them. The flaw, tracked as CVE-2026-123890, sits in the VMware Directory Service (vmdird) inside vCenter. Broadcom's advisory VMSA-2026-0009 rates it critical, with a CVSS score of 9.8. Anyone who can reach vCenter over the network can skip the login entirely and end up with administrator access, giving control of the virtual machines it manages.
The same advisory fixes four other issues: three in SDDC Manager and one in VMware Tools for Windows, the helper software installed inside Windows virtual machines. Broadcom treats the vCenter fix as an emergency change. It lists no official workaround, although restricting network access and firewalling vCenter reduce exposure.
Broadcom's advisory doesn't say the flaw was exploited, but Mandiant and Google Threat Intelligence Group, who reported it, have published their own analysis. They link the attacks, starting in early September 2026, to a suspected Chinese state-sponsored group they track as Armory Castle (previously UNC5221). According to BleepingComputer's summary of that research, the attackers first broke in through a separate zero-day in BeyondTrust Remote Support (CVE-2026-102764), moved onto internal Linux systems, then used the vCenter flaw to:
- create a new vCenter Single Sign-On (SSO) administrator account
- copy the vCenter directory database, which holds further credentials
- steal the SAML signing keys, letting them forge login tokens (a so-called Golden SAML attack) that get around multifactor authentication
- reach the ESXi hosts and pull data out of virtual machines, including Windows Active Directory database files
Who is affected
Any business running a vCenter version older than the fixed releases in the advisory. That includes standalone vCenter and vCenter deployed as part of VMware Cloud Foundation or VMware vSphere Foundation. Turning off Enhanced Linked Mode does not help: the flaw is in vCenter itself either way. The ESXi hosts themselves don't need this update, but Windows virtual machines need VMware Tools updated.
Older systems are the biggest worry. Fixes are out for vCenter 8.0 (Update 3m) and the 9.x releases, but vSphere 7.0 reached end of general support in October 2025 and patches are only available through extended support. Broadcom's FAQ says to presume vSphere 6.5 and 6.7 are affected too.
Why it matters for Australian businesses
vCenter holds the keys to everything running on your servers: file shares, line-of-business applications, accounting databases and often your domain controllers. An attacker with admin rights there can copy, change, switch off or encrypt the lot. The stolen signing keys and Active Directory data in this campaign show how one compromised console can lead to the whole network, and forged tokens can keep working even after passwords are changed.
Many smaller organisations don't manage VMware day to day; an IT provider or hosting company does. The ACSC's recent alert, Vulnerabilities are moving quickly, so patch, protect, prevent, specifically advises organisations to confirm their suppliers can promptly patch the systems they manage on their behalf.
What to do now
- Patch vCenter. Install the fixed version listed in VMSA-2026-0009 for your release. Broadcom's VMSA-2026-0009 questions and answers notes that virtual machines keep running while vCenter is updated, so the outage is limited to the management console.
- Update VMware Tools in Windows virtual machines. This closes the separate Tools flaw in the same advisory.
- Keep vCenter off the internet. The management console should only be reachable from a small number of admin machines or a dedicated management network, never directly from the internet or the general office network.
- Check for unexpected SSO administrator accounts. Review vCenter Single Sign-On users and groups and the Administrators group. Investigate anything you don't recognise rather than just deleting it.
- Check BeyondTrust Remote Support if you use it. Make sure it is fully patched for CVE-2026-102764, as that was the entry point in this campaign.
- Ask your IT provider or host. Have they patched vCenter, how is it exposed, and have they looked for signs of compromise?
- Make sure backups are offline. Keep at least one recent copy that can't be reached from vCenter or your domain admin accounts, and test a restore.
- Plan to retire unsupported versions. If you're on vSphere 7.0 or older without extended support, plan an upgrade or migration now.
If you suspect a compromise, report it through ReportCyber.
How MSP Logic can help
MSP Logic helps small and medium businesses keep on-premises servers patched and properly locked down, including VMware environments. We can check your vCenter version and exposure, apply the update, review admin accounts for anything unexpected, and make sure your backups would survive an attack. See our managed IT services and cybersecurity services, or get in touch for a quick review of your servers.
Source: BleepingComputer – VMware patches vCenter zero-day exploited in attacks since September. This article is MSP Logic's own summary and advice; read the original report for full details.