Friday, 20 November 2026

VMware zero day patch: install these builds, then hunt for spies

A China-linked group used the vCenter hole for over two months before Broadcom's fix. Here's what to install, what to do on version 7 and how to check for intruders.

Rows of rack servers with status lights in a dim data center

The short version

  • Broadcom fixed CVE-2026-123890, a vCenter authentication bypass rated 9.8 out of 10, on November 19.
  • Mandiant says a suspected Chinese espionage group exploited it as a zero-day from early September.
  • Fixed releases exist for vCenter 9.1, 9.0 and 8.0 Update 3m; version 7 needs an extended support deal.
  • Broadcom lists no workaround, and researchers say patched servers should still be checked for signs of compromise.
Quick read · 1 min

Broadcom has released the VMware zero day patch for CVE-2026-123890, a vCenter Server login bypass rated 9.8 out of 10. Anyone who can reach a vulnerable server over the network can get a full administrator session without a password.

Google's Mandiant team says a suspected Chinese espionage group exploited the flaw from early September, after first breaking in through BeyondTrust Remote Support. Once inside, the attackers created admin accounts, copied vCenter's directory database and stole signing keys that let them forge logins.

  • Install vCenter 8.0 Update 3m or the new patch builds for 9.0 and 9.1.
  • Version 7 gets a fix only under extended support.
  • There is no workaround, only firewall limits to cut exposure.

Patching does not evict anyone already inside. Check for unknown single sign-on admins and unfamiliar files on the Linux machines near vCenter.

The VMware zero day patch that admins have been waiting on is out: Broadcom fixed a vCenter Server flaw on November 19 that a suspected Chinese spy group had already been using for more than two months. The bug, CVE-2026-123890, lets someone who can reach the server over the network skip the login entirely and end up with a full administrator session.

If your company runs VMware, this is the server that controls every virtual machine you own. Whoever holds vCenter can switch servers off, copy their disks or plant software inside them. Broadcom treats this as an emergency update, rates it 9.8 out of 10 for severity and offers no workaround, so installing the fixed release is the only real answer. Below is exactly what to install, what to do if you are stuck on an older version, and how to tell whether you were hit before the fix existed.

01

Which vCenter versions get the VMware zero day patch

Every vCenter release older than the builds Broadcom lists as fixed in its advisory, VMSA-2026-0009, is vulnerable. That covers vCenter installed on its own and vCenter bundled inside VMware Cloud Foundation, vSphere Foundation and the Telco Cloud products. It does not matter whether Enhanced Linked Mode (the feature that joins several vCenter servers together) is switched on.

Here is where the fixes landed:

  • vCenter 9.1: the new patch build Broadcom released November 19.
  • vCenter 9.0: a fresh patch build from the same day.
  • vCenter 8.0: Update 3m.
  • VMware Cloud Foundation 5.x: a fixed 5.2 release, listed in the advisory.
  • Telco Cloud Platform and Telco Cloud Infrastructure: follow knowledge base article KB463116 for the steps.
  • vCenter 7.0: no public fix. Version 7 left general support in October 2025, so only customers with an extended support contract get a patch, and they need to contact Broadcom for it.

Compare the build your servers report with the fixed build for your branch in the advisory. Anything lower is exposed.

Hands on a keyboard in front of two dark monitors late at night
02

Why this flaw is worse than a typical bug

Most serious bugs need a stolen password or a careless click. This one needs neither. It sits in the VMware Directory Service, the part of vCenter that handles single sign-on, and Google’s Mandiant team says a successful attack hands the intruder a session as the built-in administrator account.

From there, the attackers in Mandiant’s investigation went much further. They created their own single sign-on admin account, copied the directory database that holds account secrets, and pulled out the signing keys vCenter uses to prove a login is genuine. With those keys, a second tool could forge login tokens (a trick security people call Golden SAML), which gets around multifactor authentication and lets an attacker pose as real users. They also took the vCenter master encryption key and database passwords, then moved on to ESXi hosts, the physical machines that run the virtual ones, and pulled Windows Active Directory files out of virtual machines.

In plain terms: patching closes the door, but if someone already walked through it, they may be holding copies of your keys.

03

Who was behind it, and how they got in

Mandiant and Google Threat Intelligence Group link the attacks to a group they now call Armory Castle, previously tracked as UNC5221 and also known as Warp Panda. It is a cyberespionage crew with a long record of breaking into network edge gear such as Citrix NetScaler and Ivanti Connect Secure.

This campaign started somewhere else. The group first broke into BeyondTrust Remote Support appliances using a separate zero-day, CVE-2026-102764, then hopped to internal Linux machines that had no endpoint detection software watching them. From those, it scanned for VMware systems and used a custom tool written in Go, which Mandiant named BONESAW, to exploit vCenter in early September.

Two details stand out. Mandiant says the group knew about this hole before VMware disclosed a different vCenter login bypass, CVE-2026-59309, on July 29, and BONESAW worked against a server that was already patched for that earlier flaw. Mandiant also says the tool works against vCenter 7.x and 8.x. A senior analyst at Google’s threat team said only a small number of organizations are confirmed compromised so far, but more targets were likely affected.

Broadcom’s own advisory does not say the flaw was exploited. The exploitation evidence comes from Mandiant, which reported the bug to Broadcom.

Close-up of network cables in a switch with one cable unplugged
04

How to check whether attackers already got in

Mandiant’s CTO Charles Carmakal put it simply: apply the fix and look for evidence of a break-in. Because the attackers were active from September, a patch installed today does nothing about access they already set up. Practical checks, based on what investigators found:

  1. Review single sign-on admin accounts. Look for any administrator account in vCenter single sign-on that nobody on your team created.
  2. Look at the Linux boxes around vCenter. The attackers parked on internal appliances with no endpoint monitoring and left web shells there. Inventory those machines and check them for unfamiliar web files and new accounts.
  3. Check your BeyondTrust Remote Support appliance. It was the way in for this campaign. Make sure the earlier BeyondTrust fix is installed and review its logs.
  4. Treat any sign of a break-in as serious. In the cases Mandiant studied, the intruders walked off with signing keys, the master encryption key and database passwords, so one bad find can mean far more than a single stolen account.
  5. Watch for odd vCenter logins. Sign-ins from internal servers that never normally talk to vCenter are a red flag.
05

Shrinking the target while you schedule the update

Broadcom says network restrictions and firewall rules can cut exposure, even though they are not an official workaround. Mandiant goes further and argues that vCenter should only accept connections from a short list of trusted admin machines, including on the single sign-on service port the attackers scanned for. It also warns that the firewall built into the vCenter appliance’s management page is too coarse to rely on, since it tends to trust a machine for every port at once and does not log blocked attempts. Put a real firewall in front of vCenter, block its outbound internet access, and send its logs to a central system your security team actually reads.

06

What else is in the same advisory

VMSA-2026-0009 fixes four more bugs. Three are in SDDC Manager, the tool that runs VMware Cloud Foundation: a SQL injection flaw rated 8.1, a local privilege escalation rated 6.7, and a command injection rated 7.2 that needs a logged-in user. The fourth is a SAML token signature bypass in VMware Tools for Windows, also rated 6.7. None has a workaround either, so update VMware Tools inside your Windows virtual machines in the same maintenance window.

07

Quick answers

Is there a workaround for CVE-2026-123890?

No. Broadcom lists none. Limiting which machines can reach vCenter lowers the risk, but only the fixed release removes the flaw.

Is vCenter 7 getting a fix?

Only for customers with extended support, who must contact Broadcom. Everyone else on version 7 should plan an upgrade to a supported, patched release.

Does patching remove attackers who are already inside?

No. The fix blocks new break-ins. Accounts, web shells and stolen keys from earlier attacks stay until you find and remove them.

You're reading the quick version.