VMware vCenter Authentication Bypass (CVE-2026-123890): What We Know So Far
Published: 20 November 2026 | Last Updated: 20 November 2026, UTC
Broadcom has patched CVE-2026-123890, a critical authentication bypass in VMware vCenter. Google Threat Intelligence Group (GTIG) and Mandiant report that the suspected PRC-nexus actor ARMORY CASTLE (formerly UNC5221) exploited the vulnerability as a zero-day in early September 2026, gaining administrator-level access. Affected organizations should apply the new fixes promptly, even if they installed July's vCenter security updates.
At a Glance
| CVE | CVE-2026-123890 |
| Affected Product | VMware vCenter, including deployments within Cloud Foundation, vSphere Foundation and Telco Cloud products |
| Severity | Critical, 9.8 (CVSS v3.1) |
| Exploitation Status | Confirmed successful exploitation reported by Mandiant in September 2026; no matching Previdian honeypot attempts observed yet as of 20 November 2026 |
| Public Exploit | BONESAW used privately in an intrusion; no public CVE-specific PoC identified as of 20 November 2026 |
| Patch Available | Yes, Broadcom VMSA-2026-0009.1 |
| Previdian Intelligence | Added to Previdian's KEV feed on 19 November 2026 at 14:55 UTC; not listed in CISA KEV as of 20 November |
What Is CVE-2026-123890?
The flaw affects the VMware Directory Service (vmdird). According to GTIG, an unauthenticated attacker who can reach the service's DCE/RPC interface on TCP port 2012 can recover an SRP-6a session key and establish a session as administrator@vsphere.local.
Mandiant recovered a Go-based exploitation tool called BONESAW, which can create SSO administrator accounts and extract the vCenter directory database (data.mdb) and Security Token Service signing material. This can enable further control of the virtualized environment. It is not a guest-to-hypervisor VM escape.
Who Is Affected?
Broadcom's advisory specifies these affected branches and remediation paths:
| Product / Branch | Fixed Version or Action |
|---|---|
| Cloud Foundation / vSphere Foundation vCenter 9.1.x | 9.1.1.0200 |
| Cloud Foundation / vSphere Foundation vCenter 9.0.x | 9.0.2.0200 |
| vCenter Server 8.0 | 8.0 U3m |
| vCenter Server 7.0 | Contact Broadcom Support if covered by extended support |
| Cloud Foundation 5.x | Apply vCenter 8.0 U3m via the applicable patching process; update SDDC Manager to 5.2.5 |
| Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 / Telco Cloud Infrastructure 3.0 | vCenter 8.0 U3m; follow KB463116 |
This is distinct from the July authentication bypass, CVE-2026-59309, which targets LDAP ports 389/636 rather than the RPC path. Fixing the July vulnerability does not fix CVE-2026-123890, as Broadcom's FAQ confirms.
Is CVE-2026-123890 Being Exploited in the Wild?
Yes. Mandiant reports that ARMORY CASTLE successfully used BONESAW against an internal vCenter server in early September, creating an SSO administrator account and exfiltrating its directory database. The intrusion began with exploitation of a separate BeyondTrust Remote Support flaw, CVE-2026-102764, followed by lateral movement. This is Mandiant's reported incident, not an observation from Previdian sensors.
Previdian added CVE-2026-123890 to its KEV feed on 19 November at 14:55 UTC based on third-party exploitation evidence. Previdian has not observed exploitation attempts targeting this vCenter CVE in our honeypot network yet (as of 20 November 2026).
Separately, Previdian recorded 75 attempted-exploitation events mapped to the earlier BeyondTrust CVE across nine source IPs between 1 and 17 November; inspected observations targeted decoy honeypots and do not establish successful exploitation. No connection between those observations and ARMORY CASTLE has been established. Previdian added the BeyondTrust CVE to its KEV feed on 16 October at 06:20 UTC, approximately 11 hours 10 minutes before CISA listed it at 17:31 UTC.
Is a Patch or Mitigation Available?
Yes. Broadcom released fixed builds on 19 November and lists no official workaround. The updates cannot be applied through vCenter Quick Patch, so follow the supported update process for your deployment. Restricting untrusted access to vCenter management services, especially TCP 2012, reduces exposure but is not a substitute for patching.
What Should Defenders Do?
- Patch vCenter urgently using the appropriate fixed build; review the 7.0 extended-support path separately.
- Restrict management access, particularly TCP 2012 and 443, to authorized administrator networks and systems.
- Investigate suspicious identity changes, including unexpected SSO administrator or machine accounts, directory database access and changes to STS signing material.
- Hunt for lateral movement, including unusual scans of TCP 2012, unauthorized SSH enablement, modified ESXi
authorized_keysfiles and hidden staging directories on VMFS volumes.
What Remains Unknown?
The full extent of exploitation beyond the incidents documented by Mandiant remains unclear. No publicly released PoC specific to CVE-2026-123890 was identified in the sources reviewed by 20 November, although Mandiant has documented working private exploit tooling.
Updates
- 20 November 2026, UTC: Broadcom's VMSA-2026-0009 advisory updated to revision 1; initial FAQ published.
- 19 November 2026, UTC: Broadcom disclosed the flaw and GTIG published details of September exploitation. Previdian added CVE-2026-123890 to its KEV feed at 14:55 UTC.
References
- Broadcom VMSA-2026-0009.1
- Google Threat Intelligence Group and Mandiant: ARMORY CASTLE Exploits vSphere
- Broadcom's VMSA-2026-0009 FAQ
- Censys advisory and public exploit assessment
- Previdian: CVE-2026-123890 intelligence
Stay Ahead of Emerging Vulnerabilities
Previdian connects early warning, exposure checks and available temporary defences in one enterprise platform. Request a demo to see how your team can use this intelligence in its vulnerability response.