Canadian Cyber Security Journal
SOCIAL:
Filed under: Featured, TechTalk

Critical vCenter Flaw CVE-2026-123890 Lets Attackers Bypass Authentication: What Canadian Teams Must Patch Now

What Happened

VMware vCenter CVE-2026-123890 is a critical authentication bypass you need to schedule now. Broadcom published advisory VMSA-2026-0009 on November 19 and rated the flaw in the VMware Directory Service at CVSS 9.8, The Hacker News reports. An attacker with network access gains unauthorized access to vCenter. Mandiant reported the bug.

Affected products include vCenter 8.0, 9.0, and 9.1, plus the vCenter builds inside VMware Cloud Foundation, including the 5.x line, vSphere Foundation, and Telco Cloud Platform and Infrastructure. Broadcom presumes vSphere 6.5, 6.7, and 7.0 are affected. Those versions left general support in October 2025 and get no fix. Broadcom lists no workaround and calls the update an emergency change. No attacks or public exploit code have been reported.

Why This Matters for Canadian Organizations

vCenter runs the virtual infrastructure behind Canadian federal departments, provincial health authorities, banks, and municipalities. Control of vCenter means control of every virtual machine it manages. Attackers know this. In August, a suspected China-nexus actor exploited vCenter flaw CVE-2026-59310 and deployed Babuk-derived ransomware on ESXi hosts. Expect the same playbook once researchers reverse the patch.

Many Canadian organizations still run vSphere 7.0 after Broadcom’s licensing changes. Those teams now face a critical flaw with no patch on their branch. A ransomware attack on a hypervisor triggers PIPEDA breach reporting duties for private firms and Law 25 obligations in Quebec. Federally regulated critical infrastructure operators face added scrutiny under Bill C-8.

What to Do

Apply the fixed build for your vCenter branch through a full update. Quick Patch does not install this fix. Check upgrade paths first, since 8.0 U3m and 9.0.2.0200 block a later move to VCF 9.1.1. Restrict access to vCenter and its directory service to dedicated management networks, and never expose vCenter to the internet. If you run vSphere 7.0 or older, isolate those servers and fund the migration now. Review vCenter logins and new administrator accounts for unexpected activity. Follow our TechTalk coverage and today’s Daily Brief for updates.

Enjoy this article? Don’t forget to share.