On 19 November 2026, Broadcom released an emergency fix for a critical VMware vCenter Server vulnerability, CVE-2026-123890, rated 9.8 out of 10. The same day, Google’s threat intelligence team and Mandiant said attackers had been exploiting it as a zero-day since early September, more than two months before the patch.
If your business runs servers on VMware vSphere, either in-house or through an IT provider, this needs attention this week.
What is vCenter, and why does this matter?
vCenter Server is the management console for VMware. From vCenter, an administrator can start, stop, copy, change and delete every virtual machine: your file servers, domain controllers, databases and backups.
That makes it one of the most valuable targets on any network. An attacker with vCenter admin access can:
- Copy entire virtual machines, including domain controllers, to steal passwords and data
- Create hidden virtual machines that security tools don’t see
- Switch off or encrypt every server at once, which is a favourite ransomware tactic
What happened
According to the advisory and research published so far:
- The flaw is an authentication bypass in the vCenter directory service. An unauthenticated attacker who can reach vCenter on the network can obtain an administrator session (
[email protected]). - Google says the root cause was predictable values in part of vCenter’s login process.
- Mandiant attributes the attacks to a suspected China-linked espionage group it tracks as ARMORY CASTLE (formerly UNC5221), using a custom tool it calls BONESAW. In at least some cases, the group first got into networks through a separate zero-day in a remote support product.
- Broadcom’s advisory (VMSA-2026-0009) says there is no workaround. Patching is the only fix.
Note: at the time of writing, Broadcom’s own advisory credits Mandiant but doesn’t itself confirm in-the-wild exploitation; that comes from Google and Mandiant’s research.
Which versions are affected?
Published reports list vCenter Server 7.0 and 8.0, along with VMware Cloud Foundation and Telco Cloud products. Reported fixed versions include:
| Product | Fixed version (reported) |
|---|---|
| vCenter Server 8.0 | 8.0 U3m |
| vCenter Server 9.x | 9.0.2.0200 / 9.1.1.0200 |
| VMware Cloud Foundation 5.x | 5.2.5 |
Always confirm the exact build numbers against Broadcom’s advisory for your version. Reports say these updates can’t be applied with vCenter’s Quick Patch and must be installed as a full update.
What to do now
1. Find out if you run vCenter
If you have more than a couple of VMware hosts, you probably do. If an IT provider manages your servers, ask them directly: “Do we run vCenter, and have you applied the VMSA-2026-0009 fix for CVE-2026-123890?”
2. Patch as an emergency change
Schedule the update now, not at the next maintenance window. Take a file-based backup or snapshot of the vCenter appliance first, following Broadcom’s guidance, and plan for vCenter (not your virtual machines) to be unavailable during the update.
3. Make sure vCenter isn’t reachable from the internet
vCenter should only be reachable from a dedicated management network or a VPN with MFA. Check your firewall for any rules that expose ports 443 or 5480 on vCenter to the internet. See our network hardening guide.
4. Look for signs that someone was already in
Because the flaw was exploited for months before the patch, patching alone isn’t enough. Check:
- New or changed accounts in vCenter Single Sign-On, especially administrators
- Logins at unusual times or from unexpected IP addresses in vCenter’s logs
- Virtual machines you don’t recognise, or VMs that were cloned, exported or had their disks copied
- New SSH access or services enabled on vCenter or ESXi hosts
- Indicators of compromise published by Google/Mandiant for this campaign
If you find anything suspicious, treat it as a security incident: isolate, preserve logs, and get specialist help before rebuilding.
5. Reduce the damage of a future vCenter compromise
- Use separate admin accounts for vCenter, with MFA through your identity provider
- Don’t join vCenter to the same Active Directory domain it manages if you can avoid it
- Keep backups isolated from vCenter, so an attacker who controls vCenter can’t delete them
Quick checklist
| Task | Done? |
|---|---|
| Confirmed whether we run vCenter (and which version) | |
| vCenter updated to the fixed build | |
| vCenter not reachable from the internet | |
| Admin accounts and SSO users reviewed | |
| vCenter logs checked since September | |
| Backups isolated from vCenter |
Virtualisation platforms often get patched less often than Windows servers because updates feel risky. This incident shows why that’s dangerous: attackers specifically look for the systems that control everything else.
Sources: Broadcom advisory VMSA-2026-0009, Google Threat Intelligence Group and Mandiant research, SecurityWeek and BleepingComputer reporting (19–20 November 2026).

