An internal vCenter server was attacked even though it had already received a fix for an earlier authentication bypass. Mandiant's 19 November investigation identifies a different flaw, CVE-2026-123890, exploited in early September 2026. Broadcom published the corresponding security advisory on 19 November.
For hosting operators, the case challenges two assumptions: that an internal management interface is outside an attacker's reach, and that a recent patch for a similarly described vulnerability covers a new one. Neither assumption held in the investigated intrusion.
The management plane was the target
Broadcom's VMSA-2026-0009 advisory identifies an authentication bypass in the VMware Directory Service. It assigns a maximum CVSS v3.1 base score of 9.8 and states that an attacker needs network access to vCenter. It lists no workaround.
Mandiant describes the technical result as disclosure of an SRP authentication session key through the directory service's DCE/RPC interface. Successful exploitation creates an authenticated session as administrator@vsphere.local. Its investigation connects the BONESAW utility to creation of an SSO administrator account and extraction of the directory database and signing material.
That is more consequential than stealing the password of one ordinary guest user. The target is the service through which administrators control a virtualized environment. A working guest application can remain available while the authority used to administer its infrastructure has been compromised.
Mandiant attributes the observed activity to ARMORY CASTLE, which it describes as a suspected PRC-nexus actor. That is the investigator's assessment, not proof that every vulnerable deployment was targeted by that group. SecurityWeek's independent 19 November reporting also distinguishes the newly disclosed issue from the earlier vCenter bypass.
The attacker reached vCenter from inside the network
The observed attack did not require vCenter to be the original internet-facing entry point. Mandiant describes lateral movement from a compromised remote-support appliance through internal Linux systems before vCenter was targeted.
An internet exposure inventory therefore answers only part of the risk question. The relevant boundary includes systems that can reach management services from inside the network, along with the identities and software entrusted with that access. A management address being absent from a public scan does not establish that it is unreachable after another appliance is compromised.
Our Check Point attack-chain analysis examines a separate gateway-to-ESXi intrusion. It is not evidence of a shared campaign or vulnerability. Both cases make internal administrative reach important, but the products, flaws and documented access paths differ.
A previous bypass patch is not the new fix
Broadcom's supplemental FAQ states that CVE-2026-123890 is distinct from CVE-2026-59309. Systems below the newly fixed versions still require the update. The same FAQ says the vCenter flaw is present with or without Enhanced Linked Mode.
For the vCenter issue, the advisory lists these fixed release identifiers:
- vCenter in Cloud Foundation or vSphere Foundation 9.1.x.x: 9.1.1.0200.
- vCenter in Cloud Foundation or vSphere Foundation 9.0.x.x: 9.0.2.0200.
- Standalone vCenter 8.0: 8.0 U3m.
Cloud Foundation 5.x and Telco products have their own response entries and associated guidance. The vCenter 7.0 entry directs customers with extended support to Broadcom Support. These identifiers are product-specific; a similarly numbered SDDC Manager update is not interchangeable with a vCenter update.
The evidence needed for a software inventory is consequently more precise than “VMware patched in November.” It needs the component, release branch and installed correction. A date in a maintenance record cannot substitute for that identity.
This advisory does not describe a VM escape
The bulletin also covers SDDC Manager and VMware Tools for Windows. Grouping them under one advisory does not give them the same entry conditions or impact.
Broadcom's FAQ explicitly says none of these issues permits code execution on an ESX host from a virtual machine, and that ESX itself is not affected by this advisory. The Tools issue stays within the Windows guest under its stated prerequisites. Those limits do not reduce the significance of administrator access to vCenter; they locate the failure in the correct security boundary.
A guest-to-host escape defeats isolation from inside a workload. Abuse of an infrastructure management service obtains authority through a different route. Calling every virtualization incident an escape would obscure the control that failed and the component that requires attention.
Emergency maintenance has an upgrade constraint
The FAQ flags a specific compatibility problem: vCenter 8.0 U3m and 9.0.2.0200 introduce a “Back-in-Time” restriction on upgrades to VCF 9.1.1. Security correction and forward-upgrade eligibility are therefore separate checks, particularly for organizations already moving between release branches.
Broadcom also says a vCenter update temporarily interrupts management interfaces while running virtual-machine and container workloads continue. That statement describes expected update behavior, not a guarantee that every customer deployment has no operational dependencies on the unavailable management service.
NHS England's 19 November alert assesses further exploitation as highly likely. Its assessment supports urgent attention; it does not establish a count of affected organizations or infections.
The September exploitation date makes this more than a forward-looking maintenance issue. For an organization whose management plane was reachable during the earlier period, a corrected version and an account of prior administrative activity answer different questions. In this case, the critical historical evidence concerns SSO identities, signing material and access to the management service, rather than whether guest workloads appeared healthy.

