Unauthorized access to VMware vCenter can place many virtual machines and their ESXi hosts at risk even when no hypervisor vulnerability is involved. On 19 November 2026, Broadcom released VMSA-2026-0009, addressing CVE-2026-123890, a critical authentication bypass in VMware Directory Service (vmdird). The maximum severity is CVSS 3.1: 9.8/10.
This is not simply a theoretical flaw. The same day, Google Threat Intelligence Group (GTIG) and Mandiant documented exploitation in early September 2026 by the espionage actor ARMORY CASTLE, which they assess as having a suspected China nexus. The attacker used a utility named BONESAW to obtain SSO administrator access and export vCenter directory data. The attribution reflects Mandiant's assessment; it does not publicly establish any particular individual's identity or a proven government sponsor.
The response must combine urgent patching with investigation of previously created access. A patched vCenter does not automatically remove an attacker-created administrator account, an SSH key added to an ESXi host, or copies of secrets already stolen.
Timeline: a zero-day exploited before disclosure
| Date | Documented development |
|---|---|
| Early September 2026 | Mandiant observes ARMORY CASTLE exploiting the vulnerability during an investigated intrusion. |
| 15 October 2026 | GTIG first describes related ARMORY CASTLE activity involving a separate BeyondTrust Remote Support zero-day. |
| 19 November 2026 | Broadcom issues VMSA-2026-0009, including this critical vCenter vulnerability and four other flaws in related products. |
| 19 November 2026 | Mandiant publishes the BONESAW investigation and post-exploitation sequence; the Canadian Cyber Centre reports documented exploitation. |
| 20 November 2026 | Operators need to inventory affected control-plane systems, apply vendor fixes and search for suspicious access predating disclosure. |
Primary evidence comes from Broadcom's security advisory and Mandiant's technical report of 19 November. The latter documents an investigated intrusion, not a reliable total number of affected organizations. As of 19 November, Censys had not identified a public exploit implementation for this new CVE, despite the observed private use.
How does the authentication bypass work?
The flaw involves vmdird, a component of vCenter Single Sign-On (SSO). Mandiant describes an unauthenticated disclosure of a Secure Remote Password (SRP-6a) session key through a DCE/RPC interface. In the documented attack, the vulnerable interface was reachable over TCP 2012.
By exploiting the flaw, an attacker can establish an authenticated session as administrator@vsphere.local without knowing that account's password. Mandiant's BONESAW analysis describes using this access to interact with directory functions, create an SSO administrator account, and export the underlying LMDB database, including data.mdb.
This is not the same as CVE-2026-59309, a previous vCenter directory service authentication bypass patched earlier in 2026. Broadcom explicitly states that the issues are distinct. Being patched against CVE-2026-59309 does not establish protection against CVE-2026-123890.
Prerequisite: the attacker must have network access to the relevant service. Direct internet exposure is not required. An adversary who compromises a support appliance or other internal server can reach interfaces that were never meant to be internet-facing.
The observed intrusion chain: BeyondTrust to ESXi
Mandiant's investigation reconstructs the following steps:
- Initial access through BeyondTrust Remote Support. ARMORY CASTLE had exploited a separate zero-day, CVE-2026-102764, described in earlier October reporting.
- Lateral movement into internal Linux appliances. Reconnaissance concentrated on VMware management interfaces, including TCP 2012, 5480 and 443.
- BONESAW against vCenter. The Go utility exploited the authentication bypass, created an SSO administrator account and exported and analyzed the directory database.
- Additional tooling such as SAWSNAKE. This tool has capabilities related to identity signing keys and SAML tokens. Its deployment alone does not prove that every available capability was used successfully.
- Administrative access and credential theft. Mandiant observed SSH being enabled temporarily through VAMI, the collection of appliance secrets and subsequent connections to ESXi.
- Activity on ESXi and VM storage. In the investigated case, the actor added SSH public keys to an ESXi root account and extracted files from virtual machine storage.
The significance is that vCenter is a control plane. Control over it may affect managed hosts, virtual machines, privileges, and snapshots according to available permissions. This does not mean CVE-2026-123890 is an escape from a guest VM to the hypervisor, nor that ESXi itself has the same flaw.
Affected and fixed versions
Broadcom's VMSA-2026-0009 response matrix lists:
| Product / component | Affected range | Fixed version or action |
|---|---|---|
| VMware Cloud Foundation / vSphere Foundation — vCenter 9.1.x | Below 9.1.1.0200 | 9.1.1.0200 |
| VMware Cloud Foundation / vSphere Foundation — vCenter 9.0.x | Below 9.0.2.0200 | 9.0.2.0200 |
| VMware vCenter 8.0 | Below 8.0 Update 3m | 8.0 U3m |
| VMware vCenter 7.0 | End of general support | Contact Broadcom with an extended-support contract |
| VMware Cloud Foundation 5.x | Prior to the specified fixed VCF stack | 5.2.5, with the appropriate vCenter update path |
| Affected Telco Cloud products | Versions listed in Broadcom's advisory | Follow Broadcom KB463116 |
Check the exact product and component. VMware Cloud Foundation 5.x may require the vCenter 8.0 U3m asynchronous patching route documented in Broadcom KB 88287. Do not bypass product compatibility requirements with an improvised upgrade.
Broadcom lists no official workaround for CVE-2026-123890. Restricting management interfaces to dedicated networks, bastions and approved administrators reduces exposure but is not a vendor security fix.
Four other issues in the same advisory
VMSA-2026-0009 also covers CVE-2026-123891 (SQL injection in SDDC Manager), CVE-2026-123892 (authenticated command injection in SDDC Manager), CVE-2026-123893 (local privilege escalation in SDDC Manager), and CVE-2026-123894 (SAML token signature validation bypass in VMware Tools for Windows in specific conditions).
These are separate issues from the vCenter authentication bypass. They have different prerequisites and patch requirements, described in the official VMware FAQ. Broadcom also clarifies that none of these issues is a guest VM escape to ESXi.
Operational response: inventory, patch and verify
1. Inventory every vCenter appliance and running build
Find standalone vCenter instances and vCenter components of VCF/VSF, including disaster recovery sites and labs with production connectivity. Record each appliance's full version and build through vSphere Client and appliance management, and compare with the Broadcom matrix.
An ESXi host's version or VMware Tools build is not a substitute for checking vCenter, which contains the CVE-2026-123890 flaw.
2. Review paths to the management plane
Determine who can reach TCP 2012 (the RPC interface identified by Mandiant), 443 (web/API, depending on architecture), and 5480 (appliance management). Include bastions, backup products, support software and internal servers that should not need these interfaces.
Internal network access should not be equated with trust. The intrusion used lateral movement after the initial compromise of an external support system.
3. Patch using the correct Broadcom release path
Schedule a controlled change and deploy the patch matching the actual product branch. Prepare validated, recoverable backups of the appliance and its settings according to VMware guidance. Review VCF and ESXi compatibility, as well as rollback plans, before the update.
The vCenter management interface and API can be temporarily unavailable during an upgrade, but the operation does not by itself stop running guest workloads, as Rapid7 notes. Validate dependencies for the specific environment.
4. Verify the patched build and system functionality
After the update, check the build actually running, SSO login, ESXi connectivity, logging and backup workflows. In environments with multiple vCenter appliances, do not assume success based on one updated instance.
5. Investigate potential pre-patch exposure
Because exploitation was observed in early September, limiting log review to 19–20 November may miss relevant activity. Choose a search window based on retention and actual network reachability; 1 September is a practical review boundary, not a verified first date of exploitation.
Digital forensics: what to look for
The following checks are informed by Mandiant's published investigation. They concern a documented campaign, not indicators guaranteed to appear in every compromise exploiting the CVE.
| Area | Relevant investigative questions | Important limitation |
|---|---|---|
| vCenter SSO / vmdird | Unexpected administrator accounts, group or role changes, unusual administrative sessions | An unfamiliar account alone does not establish the source of intrusion |
| Directory database | Unusual LMDB access or export involving data.mdb | Legitimate backup activity can look similar |
| VAMI and SSH | Unexpected enable/disable history for SSH, administrative API events, remote shell sessions | SSH may be disabled during triage despite prior malicious use |
| SAML / identity | Unexplained STS signing-key or configuration changes, suspicious SSO sessions | A tool's ability to forge SAML tokens is not proof it did so in every case |
| ESXi and VMFS | New SSH public keys, unusual root/vpxuser sessions, unexpected VMFS files or transfers | Correlate control-plane events with host-side evidence |
| Pivot hosts | BeyondTrust audit records, internal Linux systems, flows toward TCP 2012/5480/443 and unexpected outbound connections | Missing EDR on internal appliances limits visibility |
Mandiant names several malware families and utilities, including BONESAW, SAWSNAKE, BEARBONES, SLIMSAVAGE, CAGEMATCH and LAZYBONES. Campaign-specific filenames include /tmp/123, /tmp/sss and /tmp/dbr on a Linux pivot. Names are easy to change and are not standalone proof of an infection. The full report includes additional network indicators and YARA rules.
Preserve evidence before potentially destructive remediation: relevant logs, original timestamps, configuration exports, hashes, authorized images and documented chain of custody. If the directory database or SAML signing keys may have been copied, treat the incident as a potential compromise of vSphere identity trust and coordinate recovery with VMware specialists. Hastily deleting accounts or rotating infrastructure keys may destroy evidence or disrupt legitimate operations.
What remains uncertain
The total number of affected organizations is unknown. Mandiant's attribution to ARMORY CASTLE and its suspected China nexus is an intelligence assessment, not a publicly proven identification of individuals or sponsors.
The report documents some observed actions and describes additional capabilities of BONESAW and SAWSNAKE. It is not appropriate to claim that every available capability—such as STS signing-key theft or forged SAML authentication—was used successfully in every victim environment. A publicly reachable management interface alone does not prove compromise.
The absence of public exploit code as of 19 November does not make the risk theoretical: private exploitation was observed months before disclosure.
What this means for enterprise resilience
A virtualization management plane concentrates privileged identities, hypervisor management, virtual machines and sometimes backup and recovery workflows. Segmented administration, independent logging, controlled service access and tested restoration procedures are essential.
GLOV Consulting covers GLOV Solutions' established digital risk-management activities. Our earlier articles on PHP2Shell leading to ESXi data destruction and NGINX2Root affecting reverse proxies describe different technical mechanisms with the same broader lesson: an infrastructure control point can expose numerous downstream services.
Information reviewed on 20 November 2026. Digital forensics and GLOV AI are still described as upcoming services on the website; this educational publication does not claim they are commercially available. No compromise of GLOV Solutions or its customers is alleged.
Official sources and independent research
- Broadcom — VMSA-2026-0009 security advisory, 19 November 2026.
- Broadcom / VMware — official VMSA-2026-0009 FAQ.
- Google Threat Intelligence Group / Mandiant — ARMORY CASTLE Exploits vSphere, 19 November 2026.
- Canadian Centre for Cyber Security — AV26-1185, 19 November 2026.
- NHS England — Critical Zero-Day Vulnerability in VMware vCenter, 19 November 2026.
- Censys — observed exploitation, exposure and evidence limits, 19 November 2026.
- Rapid7 — patching and operational guidance, 19 November 2026.