VMware Rushed Out a vCenter Patch After a China-Linked Group Burned a Zero-Day
VMware patched a critical vCenter zero-day on November 19 after a China-linked group known as Armory Castle exploited it for more than two months.

The VMware vCenter zero-day is now patched: VMware rushed out the fix on November 19, ending an exploitation window that ran for more than two months before any fix existed. The flaw was exploited by a China-linked group tracked as Armory Castle, and the patch landed the same week as a pile of other serious disclosures, which is exactly why it deserves its own warning instead of getting buried in the roundup.
vCenter is the product that makes this serious. It is the central management plane for VMware virtual infrastructure, the console from which administrators control hosts, virtual machines, networks, and storage across an entire data center. A flaw in vCenter is not a flaw in one server. It is a flaw in the system that manages all of them, and an attacker who gets in can move from one compromised host to everything that host manages.
VMware vCenter Zero-Day: What Two Months of Exploitation Means
The timeline is the worst part. More than two months passed between the start of exploitation and the patch, which means the vulnerable window was long enough for the attackers to do patient work: map environments, steal credentials, and establish persistence that survives the patch itself. Patching the flaw closes the door. It does not evict anyone who already walked through it.
That is why the standard advice after a zero-day like this is not just to patch. It is to patch, then hunt. Check for unusual administrative activity in vCenter logs, look for new accounts or changed permissions, and review any hosts that were managed through the affected server. If your team only patches and moves on, it is doing half the job.
The attribution matters too, though it should not be overstated. Armory Castle is described as a China-nexus group, which puts this in the category of state-linked espionage rather than opportunistic ransomware. Espionage groups are quieter, more patient, and harder to detect than criminals chasing a payout. They are also less likely to announce themselves with a ransom note, which means some victims will never know they were hit unless they go looking.
The Week vCenter Was Not Alone
The vCenter patch arrived in a week crowded with serious incidents. A supply chain attack hit 178 organizations through a compromised software supplier, a ransomware group leaked customer contact data from vendors serving JPMorgan, Visa, and Mastercard, and Microsoft warned that attackers had exploited a flaw in Entra Connect Health to read tenant metadata. Any one of those would be a big week on its own. Together they are a reminder that the background rate of serious incidents has not slowed down at all.
For teams running vCenter, the action list is short and urgent. Patch now, and do not wait for a maintenance window if you can avoid it. Then check the logs for the exploitation period, rotate credentials that passed through the affected server, and confirm that no new administrative accounts appeared. If you cannot patch immediately, restrict access to the vCenter management interface to trusted networks only, and treat that as a temporary measure, not a fix.
Zero-days in management infrastructure are the kind of flaw that separates teams with a patching routine from teams with a patching aspiration. The window here was more than two months. The patch is out. The only question left is how fast you close it, and whether you check what happened while it was open.
How to Tell If You Were Hit
The uncomfortable truth about a two-month exploitation window is that many victims will not know they were hit until they look. Start with vCenter login records for the period before the patch and flag any administrative session from an unfamiliar network or at an unusual hour. Review new or modified roles, and check whether any service accounts gained permissions they did not have before. Compare the inventory of virtual machines and hosts against your records, and look for anything that appeared without a change ticket behind it. If your team uses a SIEM, search it for the indicators VMware published with the patch. None of this is exciting work, and all of it is the difference between closing a hole and closing a hole after the attacker already left with the keys.


