VMware Zero-Day Puts vCenter Administrators on Emergency Patch Duty

Avatar photo

ByRyan Mitchell

November 21, 2026

Google says the China-linked Armory Castle group exploited a critical VMware vCenter flaw for months; Broadcom and F5 have issued urgent fixes for virtualization and network-edge products.

The most urgent cybersecurity issue reported by Saturday, November 21, is an actively exploited authentication bypass in VMware vCenter. Google Threat Intelligence and Mandiant say the China-linked group Armory Castle used the flaw for more than two months before it was publicly disclosed and patched. Broadcom says there is no workaround: affected administrators should install the applicable fix and check whether attackers were already inside.

The vulnerability, CVE-2026-123890, affects VMware Directory Service and carries a critical CVSS score of 9.8. Google says Armory Castle used a tool called BONESAW to obtain an administrator@vsphere.local session, access the service’s data.mdb file and run commands through vCenter Directory Service. Reported exploitation began in early September.

That access matters because vCenter manages virtual-machine environments. A compromised administrator session could give an attacker a path into systems managed through the platform. Patching closes the vulnerability; it does not establish that an earlier intrusion did not occur.

Broadcom’s November 20 advisory update, VMSA-2026-0009.1, covers five VMware issues: CVE-2026-123890 through CVE-2026-123894. Their severity scores range from 6.7 to 9.8, but Google’s confirmed active-exploitation report concerns CVE-2026-123890. Fixed builds include vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. VMware Cloud Foundation 5.x is fixed in version 5.2.5, according to Rapid7. Broadcom directs vCenter 7.0 customers to its support channel.

CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20. TechReview.si reports a November 23 remediation deadline for federal civilian agencies. Smaller IT teams should inventory vCenter and Cloud Foundation instances, confirm versions and prioritize exposed systems. Install the vendor’s fixed build, then review authentication and service logs for suspicious administrator sessions or commands. Since exploitation reportedly began in September, historical review is essential. Teams should escalate signs of access for incident response rather than assume patching alone removes an intrusion.

F5 has also issued emergency engineering hotfixes for six critical BIG-IP vulnerabilities. The November 18 fixes cover five iRules flaws—CVE-2026-120285, CVE-2026-120292, CVE-2026-116953, CVE-2026-120722 and CVE-2026-121805—and an Access Policy Manager flaw, CVE-2026-123637. A separate high-severity SAML-related BIG-IP APM issue, CVE-2026-126822, was also reported fixed. Available reporting does not establish active exploitation of these bugs. But BIG-IP devices often sit at the network edge, so organizations should check F5’s instructions for their version and deploy applicable hotfixes promptly rather than rely on a configuration change.

A separate Wellington IT incident has raised concern among Irish credit unions using the supplier’s banking services. Ireland’s Minister of State Robert Troy said saved payee records, not account funds, were affected. Potentially exposed information included names and bank-account references such as IBANs and BICs. The material available does not establish a verified figure for affected institutions, so none is stated here.

Credit unions and other organizations relying on third-party software should confirm what data the supplier held, when the incident was detected and what notification or customer-protection steps are required. Exposed payment details can support impersonation or payment-redirection attempts even when funds were not accessed.

For small teams, the order of work is clear: address known-exploited infrastructure first, apply vendor fixes promptly, and treat patching and compromise investigation as separate tasks. A clean update is necessary, but it is not proof that a previously exposed system is clean.

Leave a Reply

Your email address will not be published. Required fields are marked *