On November 19, Broadcom released patches for CVE-2026-123890, a critical vCenter flaw that Armory Castle, a China-linked cyberespionage group, had exploited since early September. Network access could allow an unauthenticated attacker to obtain an administrator session and control the virtual machines managed by the server.
The vulnerability resides in VMware Directory Service and has a CVSSv3 score of 9.8 out of 10. According to Mandiant and Google Threat Intelligence Group, the attackers also stole the directory database and SAML signing material; the investigation linked the campaign to initial access through BeyondTrust Remote Support devices.
Check whether your environment is affected
Broadcom considers deployments running versions earlier than the fixed releases to be affected. This includes standalone vCenter and the versions integrated into VMware Cloud Foundation, VMware vSphere Foundation, VMware Telco Cloud Platform, and VMware Telco Cloud Infrastructure. The presence or absence of Enhanced Linked Mode does not change the exposure.
Broadcom's matrix lists the following fixed versions for vCenter. If you manage a telecommunications platform, the fix is provided through KB463116, not through a generic version in the table.
| Product or branch | Fixed version |
|---|---|
| vCenter 9.1.x | 9.1.1.0200 |
| vCenter 9.0.x | 9.0.2.0200 |
| vCenter 8.0 | 8.0 U3m |
| VMware Cloud Foundation 5.x | 5.2.5 |
| vCenter 7.0 | Contact Broadcom support if you have an extended support contract |
For VMware Telco Cloud Platform branches 3.0, 4.x, 5.0.x, 5.1.x, and 5.2, and Telco Cloud Infrastructure 3.0, Broadcom refers users to KB463116 for instructions. Do not assume that a patch for a different branch applies to these products.
What to do, step by step
Inventory your VMware components. Identify every vCenter and its branch, as well as SDDC Manager and VMware Tools for Windows installations. The VMSA-2026-0009 update addresses five vulnerabilities across these products, not just the vCenter authentication flaw. Also note which systems are part of Cloud Foundation, vSphere Foundation, or Telco platforms.
Compare each version against the matrix. Confirm that the installed version meets the fixed version applicable to that branch. Broadcom says VMware vCenter 7.0 will receive a patch only if the organization has an extended support contract; if so, contact support for guidance. For Telco branches, follow KB463116.
Prioritize and plan the installation. Broadcom classifies CVE-2026-123890 as critical and urges users to install the update as soon as possible. Obtain the packages and instructions for the relevant version through Broadcom's support channels. If you use Cloud Foundation 5.x, the fixed vCenter version is 5.2.5; Broadcom refers users to its asynchronous patch guide KB88287.
Update the other affected products. VMSA-2026-0009 also fixes three SDDC Manager flaws and one VMware Tools for Windows flaw. For Tools, Broadcom specifies the fix as 13.1.5.0 for the 13.x branch and 12.5.5 for the 12.3.x, 12.4.x, and 12.5.x branches. Check the SDDC Manager versions in the advisory matrix: its fixed versions are not necessarily the same as those for vCenter.
Limit exposure while you update. Broadcom does not provide an official workaround for CVE-2026-123890. It does note that network restrictions and firewall controls can reduce exposure; use them as temporary measures, not as a substitute for the patch. The attacker needs network access to the vulnerable vCenter.
Investigate signs of prior access. Patching does not establish whether the system has already been compromised. Mandiant documented the creation of SSO administrative accounts, theft of the directory database and SAML signing keys, and the use of tools and backdoors. Review SSO accounts and available logs for unauthorized activity; if you find signs of compromise, treat the case as a potential intrusion and follow your organization's response process.
Expand the review to the internal network. In the campaign described, Armory Castle moved from BeyondTrust devices to internal Linux systems and then searched for VMware infrastructure. Mandiant observed persistent access tools on Linux and activity targeting ESXi and virtual machines. If there was exposure, include those related systems in the investigation rather than limiting the review to the vCenter server.
Mistakes that can leave the risk unaddressed
Waiting for an official temporary fix is not an option: Broadcom says there are no workarounds for these vulnerabilities. Network filtering can limit who can reach the server, but it does not fix the flaw or prove that there was no prior access.
You should also not delay the review because the environment uses a particular link configuration. The advisory states that Enhanced Linked Mode does not change the impact. The check should cover all affected instances and products, including components deployed as part of a larger platform.
Another mistake would be to install a vCenter update and consider the entire task complete. The advisory includes separate vulnerabilities in SDDC Manager and VMware Tools for Windows, each with its own fixed-version matrix. In addition, Mandiant observed that attackers could extract material that enables them to forge SAML tokens and maintain access; therefore, updating and checking for compromise are separate actions.
Finally, do not treat an unpatched vCenter 7.0 version as protected. Broadcom makes the fix conditional on extended support. Confirm that coverage with the vendor and, in the meantime, restrict network access and assess the system's exposure.
The VMSA-2026-0009 update was published on November 19, and Broadcom updated the advisory the following day to clarify the affected VMware Tools versions. The immediate priority is to determine which branches are still installed and apply the fix that corresponds to each one.
Sources: BleepingComputer, Network World, SecurityWeek, Google Cloud Blog, Support Portal