deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Broadcom patches actively exploited 9.8-rated vCenter authentication bypass CVE-2026-123890

Broadcom has patched a critical 9.8-rated authentication bypass in vCenter Server that Google says was exploited for months by an espionage group; CISA has added it to its KEV catalog.

Broadcom patches actively exploited 9.8-rated vCenter authentication bypass CVE-2026-123890

What happened

Broadcom has patched a critical authentication bypass in VMware vCenter Server that was already being exploited in the wild, according to a security write-up on dev.to. The patch landed on November 19, 2026, and covers CVE-2026-123890, a flaw in the VMware Directory Service rated 9.8 under CVSS 3.1. Its impact is blunt: anyone able to reach a vulnerable vCenter deployment over the network can obtain a session as [email protected] without entering a password.

Google's Mandiant attributes the activity to a suspected China-nexus espionage group it tracks as Armory Castle, previously labeled UNC5221, and estimates the group has used the bug since at least early September. CISA added the CVE to its Known Exploited Vulnerabilities catalog on November 20, the day after the patch shipped.

How the flaw was used

Citing incident reporting from Google Threat Intelligence, the dev.to article describes the vCenter bug as one stage in a larger intrusion rather than the initial entry point. In the observed incidents, attackers first compromised the environment through a zero-day in BeyondTrust Remote Support, then used a private tool to seize control of vCenter. From there they created an extra SSO administrator account, took a copy of the directory database, forged authentication tokens that get around multi-factor authentication, planted an SSH key on an ESXi host, and extracted Active Directory data from a Windows VM's disk.

Patching and version status

The fixes arrive in Broadcom's VMSA-2026-0009, which also resolves three SDDC Manager vulnerabilities and a flaw in VMware Tools for Windows. For vCenter itself, the patched builds are 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, while VMware Cloud Foundation 5.x is fixed in 5.2.5. There is no interim workaround, and the Quick Patch facility cannot deliver this particular update. Running virtual machines stay online while the appliance updates. Current build numbers can be confirmed in the vSphere Client's Summary tab, on the appliance management page served at port 5480, or through PowerCLI.

vCenter 7.0 is the awkward case: it has no public fix and left general support in October 2025. Extended-support customers are advised to raise the matter with Broadcom directly, and organizations on 7.0 without that contract face an upgrade rather than a patch.

Installing July's vCenter login fix, CVE-2026-59309, does not help here. According to the report, Google observed the new bug being exploited against a server that already carried the July update. ESXi hosts are not directly affected, and none of the flaws in the advisory allow a virtual machine to escape to its host.

Checking for compromise

Because exploitation began well before the patch existed, applying the update does not evict attackers who are already inside. The recommended checks are to inspect the SSO Administrators group for unrecognized @vsphere.local accounts, look for signs of SSH being toggled on or off via the appliance API, and audit ESXi hosts for SSH keys that no administrator added.

Why it matters

vCenter concentrates control over an organization's entire virtualization estate, so an unauthenticated path to the administrator account functions almost like a master key: hosts, virtual machines and, as the reported intrusions demonstrate, connected identity infrastructure such as Active Directory all become reachable. Two details raise the urgency further. First, exploitation since at least early September means unpatched environments cannot assume they are clean; patching and threat hunting have to happen together. Second, the bug worked against a server already fixed for July's earlier login flaw, a reminder that closing one authentication hole does not neutralize the next. Environments still on vCenter 7.0, which has no available fix at all, face the hardest choice between extended-support arrangements and a full platform upgrade.

  • #vmware
  • #vcenter
  • #security
  • #zero-day
  • #virtualization

Related posts