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
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 [email protected] without a password.
This one is already being used. Google's Mandiant says a suspected China-nexus espionage group it calls Armory Castle (formerly UNC5221) has exploited it since at least early September. CISA added it to its Known Exploited Vulnerabilities catalog on November 20.
In the incidents Google described, the attackers first broke in through a BeyondTrust Remote Support zero-day, then used a private tool to take over vCenter. They created a new SSO admin, copied the directory database, forged login tokens that bypass MFA, added an SSH key to an ESXi host and pulled Active Directory data off a Windows VM's disk. The vCenter bug wasn't the front door. It was the key to everything once they were inside.
What to do:
- Check your build in the vSphere Client Summary tab, on the appliance page at port 5480, or with PowerCLI.
- Update to vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. VCF 5.x is fixed in 5.2.5. There's no workaround, and Quick Patch can't apply this fix. Running VMs keep running during the update.
- vCenter 7.0 has no public fix. It left general support in October 2025. Extended-support customers should ask Broadcom, and everyone else should plan the upgrade now.
-
Look for signs of a break-in, because patching doesn't evict anyone already inside. Review the SSO Administrators group for unknown
@vsphere.localaccounts, look for SSH being switched on and off through the appliance API, and check for SSH keys you didn't add on your ESXi hosts.
If you patched July's vCenter login bug (CVE-2026-59309), you still need this update. Google saw the new bug used against a server that already had the July fix.
ESXi hosts themselves aren't affected, and none of the bugs let a VM escape to its host. The same advisory, VMSA-2026-0009, also fixes three SDDC Manager bugs and a VMware Tools for Windows flaw.
Sources
- Broadcom VMSA-2026-0009: VMware vCenter, SDDC Manager and VMware Tools updates
- Broadcom VMSA-2026-0009 questions and answers
- Google Threat Intelligence: ARMORY CASTLE exploits vSphere
- CISA Known Exploited Vulnerabilities catalog
- CISA adds four known exploited vulnerabilities to catalog (November 20, 2026)
- NVD: CVE-2026-123890
- Rapid7: CVE-2026-123890, critical authentication bypass in VMware vCenter
- SecurityWeek: newly patched VMware vCenter flaw exploited as zero-day
- Help Net Security: VMware vCenter zero-day exploited for months before patch
- Mandiant VCSA Hardening and Logging Tool
This is the short version. The full guide, with every step and source, is on GeekSpark.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.