- SMB/SME
- Enterprise
· ASC Editorial Team
Hijacked Through vCenter: A VMware Zero-Day Exploited Since September
On 19 November 2026, Broadcom fixed CVE-2026-123890, a critical flaw in VMware vCenter, the server that manages most VMware estates. The flaw is in vCenter's directory service, and it lets an attacker who can reach vCenter over the network get in without logging in. Broadcom lists no workaround.
The same day, Google's Mandiant and Threat Intelligence Group said a suspected China-linked espionage group, which it calls ARMORY CASTLE, has exploited the flaw since early September 2026, more than two months before the fix. Broadcom's advisory doesn't say whether the flaw has been exploited, but on 20 November CISA added it to its list of known exploited vulnerabilities.
Google describes how the attackers worked. They first got in through a separate flaw in BeyondTrust Remote Support, then moved to internal Linux systems and on to vCenter. There, they created their own administrator account and stole vCenter's directory database and the key it uses to sign logins. That let them forge sign-ins and get past multi-factor authentication. From vCenter they reached the ESXi hosts and copied files out of virtual machines, including Windows Active Directory databases.
Two details matter if you patched vCenter recently: - The attackers used the flaw against a vCenter that was already patched for CVE-2026-59309, a similar flaw fixed in July. That update doesn't protect you from this one. - Google says the attackers' tool targets vCenter 7 and 8. vCenter 7 reached the end of general support in October 2025 and has no public fix. Broadcom tells customers with extended support to use their support channel, and recommends upgrading.
Whoever controls vCenter controls every virtual machine it manages. The attackers didn't need to break into each server: copying a domain controller's disk from the hypervisor gave them the Active Directory database. This is the second time this month that attackers have reached VMware through another system. In the Check Point gateway attacks, they moved from a firewall to an ESXi host.
Three steps follow.
First, patch. vCenter 8.0 is fixed in 8.0 U3m, and VMware Cloud Foundation customers should follow Broadcom's advisory, VMSA-2026-0009. Broadcom treats it as an emergency change. If you run vCenter 7, talk to Broadcom or your support partner now about extended support or upgrading.
Second, limit who can reach vCenter. Google advises allowing only trusted management addresses to reach vCenter's management ports, including port 2012, which the exploit uses, and blocking outbound connections vCenter doesn't need. vCenter should never be reachable from the internet.
Third, look for signs that someone has already been in, because the attacks started long before the patch. Check vCenter's single sign-on for administrator accounts nobody created, for SSH being turned on unexpectedly, and for unfamiliar files in /tmp. Google's report lists the file names and detection rules. If you find anything, treat it as an incident: the attackers may hold signing keys and passwords that outlast the patch, and those need replacing.
If someone had created an extra administrator account in your vCenter in September, would you have noticed?
Source: Google Threat Intelligence: ARMORY CASTLE exploits vSphere
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.