A critical VMware vCenter zero-day vulnerability, CVE-2026-123890, was exploited before a patch was released, Google Threat Intelligence and Mandiant report. Broadcom published security advisory VMSA-2026-0009 on November 19 and updated it on November 20. The authentication-bypass issue carries a CVSS 9.8 score and affects the administrative control plane used across virtualized data centers.
Security researchers attribute the observed campaign to ARMORY CASTLE, a suspected China-linked espionage group. Their forensic investigation places exploitation in early September 2026. That attribution is an assessment by Google and Mandiant, not a legal finding or an announcement by the Chinese government.
What the vCenter Zero-Day Reveals
Broadcom describes CVE-2026-123890 as an authentication-bypass vulnerability in VMware Directory Service. An attacker with network access to an affected vCenter system may exploit the flaw to bypass authentication and obtain unauthorized access. The advisory assigns critical severity and states that no workaround is available. Organizations should follow the vendor’s version-specific remediation guidance rather than rely on speculative firewall rules as a replacement for the fix.
Google Threat Intelligence Group and Mandiant published a separate technical analysis on November 19. They describe how ARMORY CASTLE used a custom exploitation utility, tracked as BONESAW, as part of a broader intrusion that crossed several enterprise systems. Researchers observed abuse of vCenter identity infrastructure, followed by access to ESXi environments and attempts to collect sensitive data.
The observations are based on the researchers’ investigation of actual attacker activity; they should not be generalized to every vCenter deployment. Broadcom’s alert confirms the vulnerable product versions and remediation. Mandiant provides the evidence that the vulnerability was exploited as a zero-day.
Which VMware Versions Need Attention?
Broadcom’s VMSA-2026-0009.1 response matrix lists different fixed releases according to the deployed product line. The table below summarizes entries for CVE-2026-123890; administrators must review the official advisory for their exact environment.
| Product / branch | Vendor-listed remediation | Important note |
|---|---|---|
| VCF / vSphere Foundation vCenter 9.1.x | 9.1.1.0200 | Use the supported suite update sequence. |
| VCF / vSphere Foundation vCenter 9.0.x | 9.0.2.0200 | Check dependency and compatibility guidance. |
| vCenter Server 8.0 | 8.0 Update 3m | Match the appropriate patch build to the deployment. |
| vCenter Server 7.0 | Contact Broadcom Support with extended support | Do not imply a general public fix is available for all installations. |
| VMware Cloud Foundation 5.x | 5.2.5 | Consult the async patching guidance and support matrix. |
| Telco Cloud products | Follow KB463116 | Several product branches have separate instructions. |
The same security notice also covers four additional CVEs affecting VMware Tools and SDDC Manager components. Those flaws have distinct severity ratings, attack conditions and fixes. The CVSS 9.8 score and confirmed exploitation story here refer specifically to CVE-2026-123890; they must not automatically be assigned to the other issues.
Timeline combines vendor publication dates and observations attributed to Google Threat Intelligence and Mandiant.
Why a Compromised vCenter Can Threaten Entire Virtual Environments
vCenter is not simply another server in a data center. It is the management plane for vSphere environments: administrators use it to configure ESXi hosts, manage virtual machines, enforce permissions, monitor infrastructure and coordinate operations. Unauthorized administrative control can therefore create an opportunity to move across the virtualization estate.
In the investigated incident, Mandiant described efforts involving Single Sign-On infrastructure, credential material and ESXi hosts. These are especially sensitive areas because recovery from a compromise of identity and management services can require more than reinstalling one application or rotating a single password. Investigators need to determine the scope of identity exposure and whether attackers gained persistence beyond the originally affected appliance.
A useful analogy is a building’s master access-control console. A compromise of an individual tenant system is serious, but a compromise of the console governing many tenants changes the scale and complexity of the response. This does not mean every exploited vCenter results in full hypervisor compromise, only that the trust relationship makes the risk unusually consequential.
What Administrators Should Do Now
Identify vCenter versions, support status, management interfaces and network paths. Prioritize internet-reachable or broadly accessible administration services.
Use Broadcom’s exact product and branch matrix. Plan backups, maintenance windows and tested rollback procedures, not undocumented mitigation claims.
Review relevant authentication, SSO, account-creation and management-access records, including evidence predating public disclosure in September.
Audit unexpected administrator accounts, changes to identity components, certificates and privileged ESXi access. Consider professional incident response if suspicious activity appears.
Restrict vCenter management access to trusted administrative paths and hardened privileged workstations. Network controls complement—not replace—patches.
Check integrity of offline configuration backups and restoration procedures. A snapshot alone is not a complete compromise-recovery plan.
Google’s investigation includes threat-hunting material and hardening guidance for defenders. Security teams should review it alongside their own logs and Broadcom documentation without treating published indicators as exhaustive. If there is evidence of unauthorized access, consider isolating management paths, preserving forensic artifacts and involving qualified responders before performing actions that could destroy evidence.
Related Servers.News coverage: our critical PHP vulnerability report examines another patch-prioritization scenario, while the server backup and disaster-recovery guide explains why recovery must be independently validated.
Administrator FAQ
Can network filtering replace the security update?
No vendor-supported workaround is listed for CVE-2026-123890. Tight management-network restrictions can reduce exposure, but affected supported installations should follow the official patch instructions.
Is VMware vCenter 7.0 fixed by the normal 8.0 release?
No. Broadcom says customers running the 7.0 branch should contact support if they have an extended-support contract. Do not apply an unrelated product branch update.
Does the Google report prove every affected server was hacked?
No. It establishes observed exploitation during an investigated intrusion. The overall number of affected organizations has not been confirmed.
Why hunt for compromise after patching?
Software remediation closes the defect but may not eliminate attacker-created identities, stolen secrets or other persistence established before the patch.
This is an urgent control-plane security update. Administrators should match their exact vCenter branch to Broadcom’s patch matrix, investigate suspicious historical activity and treat identity compromise as a separate response challenge.







