Suspected Chinese Spies Used a VMware vCenter Zero-Day for Months
Broadcom patched a critical VMware vCenter flaw on November 19, more than two months after suspected Chinese spies began using it. Google says the group, Armory Castle, chained it with a BeyondTrust zero-day to take over virtualization servers and forge logins. Companies that patch may still need to hunt for intruders already inside.
Broadcom fixed CVE-2026-123890, rated 9.8 out of 10, in advisory VMSA-2026-0009 on November 19, 2026.
Attackers exploited the vCenter flaw since at least early September, more than two months before the fix.
Google attributes the attacks to Armory Castle, a suspected China-nexus group formerly tracked as UNC5221.
Fixed versions are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m; version 7.0 has no public patch.
Mandiant found the flaw and reported it to Broadcom.

A hidden door into the data center's control room
The vCenter flaw let an attacker on the network become a full administrator without needing a password. vCenter is the software companies use to manage fleets of virtual machines, so taking it over means taking control of many servers at the same time.
The vulnerability, CVE-2026-123890, sits in the VMware Directory Service. It lets an attacker leak a session key over a network port, which hands a remote attacker an administrator session. Broadcom rated it 9.8 out of 10 and said there is no workaround.
Broadcom released the fix on November 19 in advisory VMSA-2026-0009, along with fixes for four flaws in SDDC Manager and VMware Tools for Windows. The advisory calls the vCenter fix an emergency change. It does not say the flaw was already being exploited.
Mandiant says the exploit works against vCenter versions 7.x and 8.x. Broadcom fixed the issue in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. Companies using VMware Cloud Foundation or vSphere Foundation get the same fixes through those software bundles.
Broadcom said this bug is separate from a vCenter login flaw it disclosed on July 29. The company put it plainly:
"CVE-2026-123890 is a new and distinct issue."
How did the attackers get in?
The spies got in through a second zero-day in BeyondTrust Remote Support, a remote access tool help desks use to reach other machines. Google's Threat Intelligence Group and Mandiant laid out the chain in a report published November 19.
From the remote support box, the group installed web shells on internal Linux appliances that had no endpoint security software. From there, it used a custom tool, BONESAW, to exploit vCenter. The tool copied vCenter's identity database and added a new single sign-on administrator account.
Before reaching vCenter, the group had scanned the network for VMware management ports. It also turned on SSH access through the vCenter management interface and took the master encryption key and the database password. It then turned SSH back off to mask its activity.
A second tool, SAWSNAKE, used the stolen signing keys to forge login tokens. This so-called Golden SAML technique lets an attacker impersonate any user while skipping multifactor checks. The group then moved to an ESXi host, pulled Windows domain files from a virtual machine and sent them out.
Google's research also found that the attackers knew about the vCenter bug before the earlier flaw was disclosed in July. They targeted a vCenter server in early September that had already been patched for that first bug. Google described the activity as a significant step for the group:
"BONESAW represents a significant expansion into post-compromise use of zero-days."
Who is Armory Castle?
Google tracks Armory Castle as a suspected China-nexus espionage group, formerly known as UNC5221. It attributes this campaign to the group with moderate confidence, based on similar tools and techniques.
The report does not name the victim or its industry. It describes the target as a high-priority virtualized environment. Google found two zero-days and three separate sets of malware in a single breach, a sign of a well-funded team.
The link to BeyondTrust is not new. Google and Mandiant published a report on the Remote Support zero-day on October 15. BeyondTrust has already patched that flaw in its BT26-05 update, and Google urges anyone who has not applied it to do so now.
Armory Castle targets the places security teams rarely look. Appliances such as vCenter and remote support servers often cannot run endpoint detection software, which makes them quiet targets. One backdoor, LAZYBONES, communicated through Slack, so its commands blended into normal office traffic.

Why patching alone may not be enough
Patching the flaw does not remove attackers who already have a foothold. If they hold stolen signing keys or a hidden admin account, they can come back.
Charles Carmakal, Mandiant's chief technology officer, made the point in a public LinkedIn post on the disclosure:
"Organizations should both apply the patches and examine their systems for evidence of compromise"
Google's report gives security teams a list of warning signs. It includes new SSH access turned on through the vCenter management interface and curl downloads into temporary folders. It also includes SSH from Linux appliances to ESXi hosts and Slack traffic leaving servers. The report adds detection rules that teams can load into their security tools.
Google also warns that the firewall built into vCenter is weak. Anyone with access to the management interface can disable it, and the attackers did. Mandiant recommends a hardening tool that blocks traffic by default and sends logs to a central system.
Version 7.0 has its own problem. General support for it ended in October 2025, and Broadcom lists no public patch for it. Customers on 7.0 with extended support have to request patches through that channel. Everyone else on 7.0 stays exposed until they upgrade to a supported version.
What does this mean for Silicon Valley companies?
This attack shows that the plumbing of the data center is now a top target. Virtualization, remote support and identity systems hold the keys to everything else, yet many of these appliances cannot run the security tools that protect laptops.
That gap is a business problem as well as a technical one. Many companies run vCenter in private clouds, test labs and server rooms. A spy with control of vCenter can copy virtual machines whole, which can expose source code, customer data or model weights in one move.
Attacks are also getting faster. A Sparknify report on November 17 covered Google's finding that attackers now use AI agents to turn published patches into working exploits. Zero-day exploits averaged 11 a month in 2026 but jumped to 22 in August. When the patch itself is the blueprint for an attack, the window to patch shrinks to days or hours.
Pushing emergency patches into production carries its own risk. IT teams this month already saw upgrades take systems down. Vendors also face questions about disclosure, since Broadcom's advisory did not mention the attacks and left that job to Google and the press.
Boards will ask harder questions too. Once vCenter is breached, a company may need to rebuild its identity system, reset every privileged account and check every virtual machine. That work takes weeks and pulls engineers away from product plans, so prevention costs less than cleanup.
Security leaders will likely demand more monitoring for appliances that cannot run agents. Expect a push for more logging, network segmentation and identity checks around admin tools. For security startups, that points to products that watch infrastructure from the outside.
Five things will show which way this goes.
Whether CISA adds CVE-2026-123890 to its known exploited list in the coming weeks.
How many vCenter 7.0 servers remain online without a public fix through early 2027.
New victim disclosures or breach filings tied to Armory Castle in the next few months.
Whether Broadcom updates VMSA-2026-0009 to note the in-the-wild exploitation.
More zero-days found in remote support and virtualization appliances during 2027.
The patch is out, but for some companies the intruders may already have the keys.
Subscribe to Sparknify for tech news and the people behind it.
Questions & Answers
Q1: I run a cybersecurity startup with a vCenter and ESXi monitoring tool. How can I get in front of IT leaders worried about the Armory Castle attack?
Companies are looking for ways to monitor vCenter, ESXi and other appliances that cannot run an endpoint agent, the gap Armory Castle used for months. Founders with a product for that problem can explore brand partnerships and PR campaigns at sparknify.com/advertising.
Q2: Should IT leaders move fast to patch vCenter under Broadcom's advisory, even though emergency patches sometimes cause outages?
Broadcom calls the fix an emergency change, and Google urges companies to patch as soon as possible. Teams should still test it on one server first and keep a rollback plan. Upgrades caused several outages this month, as covered in how CIOs are rebuilding their backup plans.
Q3: Is outdated, unsupported infrastructure like vCenter 7.0 a broader risk to critical systems in the United States?
vCenter 7.0 has no public fix because general support ended in October 2025, so those servers need an upgrade or extended support. Aging networks cause trouble beyond hacking too, as when old air traffic routers halted every US flight on November 13.













Comments