VMware vCenter CVE-2026-123890: Exploited Zero-Day, How to Check, Patch and Spot a Break-In
On November 19, 2026, Broadcom patched CVE-2026-123890 , a critical authentication bypass in the VMware Directory Service inside vCenter Server. It's rated 9.8 (CVSS 3.1). Anyone who can reach vCenter over the network can get a session as administrator@vsphere.local without a password. This one is already being used. Google's Mandiant says a suspected China-nexus espionage group it calls Armory…
On November 19, 2026, Broadcom released a patch for a critical authentication bypass vulnerability, CVE-2026-123890, affecting VMware vCenter Server. This vulnerability, rated 9.8 on the CVSS scale, allows unauthorized access to a vCenter session as administrator@vsphere.local without a password. It has already been exploited, according to Mandiant, by a suspected China-nexus espionage group known as Armory Castle (previously UNC5221) since early September.
CISA has listed the vulnerability in its Known Exploited Vulnerabilities catalog. The hackers typically gain access through a zero-day exploit in BeyondTrust Remote Support, then employ a private tool to assume control over vCenter. They create a new SSO admin, duplicate the directory database, forge login tokens to circumvent MFA, append an SSH key to an ESXi host, and extract Active Directory data from a Windows VM's disk. This zero-day is not the initial breach; it serves as the gateway to the compromised system.
To address this issue, verify your vCenter build via the vSphere Client Summary tab, the appliance page at port 5480, or with PowerCLI. Update to vCenter 9.1.1.0200, 9.0.2.0200, or 8.0 U3m. vCenter 5.x is secured in version 5.2.5. There is no interim solution, and Quick Patch is unable to implement this fix. Hosted VMs remain operational during the update process.
However, vCenter 7.0 has no public fix, as it had general support terminated in October 2025. Organizations with extended support should reach out to Broadcom, while all others should schedule the upgrade promptly.
Post-patch, monitor for indications of an intrusion, as the patch does not expel existing intruders. Check the SSO Administrators group for unfamiliar @vsphere.local accounts, watch for SSH on/off toggling via the appliance API, and scrutinize ESXi hosts for unapplied SSH keys. Note that even if you patched the July vCenter login vulnerability (CVE-2026-59309), this update is still necessary.
Google observed the new exploit used against a server that had already received the July fix. The advisory VMSA-2026-0009 also resolves three SDDC Manager issues and a VMware Tools for Windows flaw. The comprehensive guide, including all steps and sources, is available on GeekSpark.
Rewritten by urgent.news; may contain errors — check the original.
Source: dev.to