Broadcom published advisory VMSA-2026-0009 on 19 November 2026, disclosing a critical authentication bypass in the VMware Directory Service used by vCenter. The flaw, tracked as CVE-2026-123890, carries a near-maximum CVSS score of 9.8. Worse: it was already being exploited in the wild by a China-linked espionage group as early as September 2026 — two months before a patch was even available (securityonline.info).
vCenter is the management console that sits behind most virtualized server environments — the kind of infrastructure many Swiss SMEs and their IT providers rely on to run multiple servers on fewer physical machines. If you don't know whether your business uses vCenter, this is the week to ask your IT provider directly.
What exactly is broken
According to Broadcom, a malicious actor with network access to vCenter can exploit this flaw to bypass authentication entirely and gain unauthorized, administrator-level access to the system — no valid credentials required (The Hacker News). Broadcom lists no workaround. There is no temporary setting, no firewall rule, no configuration change that neutralizes this on its own. Patching is the only fix.
Broadcom's own advisory Q&A confirms this is a new, distinct vulnerability from an earlier vCenter authentication bypass disclosed in July — so businesses that already patched that one are not automatically protected now. The advisory also clarifies that vCenter itself is affected, while the underlying ESX hypervisor is not (Broadcom VMSA-2026-0009).
Why the timeline matters
This is not a theoretical risk disclosed cautiously ahead of attacks. Researchers report real-world exploitation by a sophisticated, state-linked group starting roughly two months before any fix existed. That means some organizations running vCenter consoles reachable from untrusted networks may already be compromised without knowing it — espionage-motivated attackers typically prioritize staying hidden over causing visible damage.
What to do today
- Identify your vCenter version. Fixed versions exist for all currently supported branches: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, and 5.2.5.
- Patch immediately if you're on a supported branch — there is no workaround to buy you time.
- Check for vCenter 7.0. That version reached end of general support and has no public fix listed. If you're still running it, plan an urgent migration to a supported version — staying on 7.0 now means staying permanently exposed.
- Restrict network access to the vCenter management interface to trusted administrative networks only, even after patching, since this console should never be reachable from the open internet.
- Ask your IT provider directly whether any of your virtualized infrastructure runs vCenter, and whether it has already been patched against VMSA-2026-0009.
The bigger pattern
This is the second vCenter-related story in a week: on 17 November we covered how a five-year-old, already-patched VMware bug (Log4Shell) still compromised an entire software supply chain simply because a vCenter instance was never updated. The lesson repeats itself: virtualization platforms are high-value targets precisely because one compromised console can hand attackers your entire server fleet — not just one machine.
AI-accelerated attacks, state-linked espionage groups, and exploit code that appears within hours of disclosure are now a daily reality for any business running internet-facing or network-reachable infrastructure. We track these developments continuously so Swiss SMEs don't have to monitor security advisories themselves.
If you're unsure what's running in your server room or whether your virtualization platform has ever been patched, The Mejlerö Company GmbH (Flitz.ai) in Engelberg offers a free network analysis and a free one-hour consultation for businesses in Obwalden, Nidwalden, Lucerne and Zurich. Beyond patching advice, their team helps SMEs automate routine IT and security administration so these checks don't fall through the cracks between advisories.