If your business runs its servers on VMware, the update Broadcom released on November 19 is not one to leave for the next maintenance window. It fixes a hole in VMware vCenter that lets someone on your network get in as the top administrator without a password, and Google's Mandiant team says attackers have been using it since early September.
What happened
Broadcom, the company that owns VMware, published security advisory VMSA-2026-0009 on November 19. The most serious fix is for vCenter, rated 9.8 out of 10. Broadcom's own wording is that someone with network access to vCenter "may exploit this issue to bypass authentication and gain unauthorized access to the system." It calls the update an emergency change and says there is no workaround.
The same day, BleepingComputer reported that Mandiant and Google's threat intelligence group had documented a suspected Chinese state-backed group using this hole since early September, before any fix existed. Broadcom's own advisory says it isn't aware of attacks, so the attack reports come from Google's researchers, not from VMware.
According to that reporting, the attackers didn't start with VMware. They first broke into a BeyondTrust remote support system, moved across the internal network, then used the vCenter hole to create their own administrator account and copy vCenter's directory database, which holds sign-in information. They also had tools to pull out the keys vCenter uses to sign logins, which can be used to fake sign-ins and get past multi-factor authentication, the extra login code most of us rely on.
What this means in plain English
A lot of businesses don't run one physical server per job anymore. They run several "virtual" servers on one or two big machines, and vCenter is the control panel that manages all of them. Whoever controls vCenter can switch servers off, copy them, or read what's on them. This hole lets an attacker who is already somewhere on your network take over that control panel without knowing any password.
It also comes with an uncomfortable detail. vCenter version 7 is affected, but it reached the end of general support in October 2025, and there is no public fix for it. Only customers with a paid extended support contract can request one from Broadcom.
Why a small business should care
This is the box that runs everything and gets touched the least, because nobody wants to be the one who breaks it. In smaller shops it's common for vCenter to sit a few versions behind for years. If an attacker gets into it, they don't just get one computer. They get your file server, your accounting server, your production systems and often your backups, all at once.
The attack described here also shows how break-ins actually happen: one weak spot leads to the next. A remote access tool, a forgotten appliance, then the control panel for everything.
Who's affected
Anyone running VMware vCenter older than 8.0 U3m, 9.0.2.0200 or 9.1.1.0200.
Anyone still on vCenter 7.0 (no public fix) or 6.7 and 6.5, which Broadcom no longer checks and which should be assumed affected.
VMware Cloud Foundation 5.x customers (fixed in 5.2.5).
Windows virtual machines running older VMware Tools, which got a separate, less serious fix in the same advisory (VMware Tools 13.1.5.0 or 12.5.5).
What to do: everyone
Find out whether your business uses VMware at all. If you don't know, ask whoever looks after your servers.
If you do, ask them to confirm vCenter is on 8.0 U3m, 9.0.2.0200 or 9.1.1.0200 or newer, and get the answer in writing.
Ask them to check vCenter for administrator accounts nobody recognizes, since the attackers in this case created their own.
Make sure only the people and computers that need vCenter can reach it on the network. Broadcom says this reduces risk, but it is not a fix.
What to do: if you run the business
If you're on vCenter 7 or older, treat this as a budget question, not an IT ticket. You either pay for extended support or plan an upgrade, and both take time. Put it on the agenda now rather than after something goes wrong. And confirm your backups are stored somewhere vCenter can't reach, so a takeover of the control panel doesn't take your backups with it.
Questions to ask your IT provider
Do we run VMware vCenter, and what version is it on today?
Was the November 19 update installed, and when?
Who has administrator access to vCenter, and has anyone checked for accounts that shouldn't be there?
If vCenter were taken over, would our backups survive?
Sources
BleepingComputer: VMware patches vCenter zero-day exploited in attacks since September
Kudelski Security: VMware vCenter Critical Authentication Bypass
Broadcom (VMware): VMSA-2026-0009: Questions & Answers
Contact Nautalex to see how we can help you with keeping your VMware servers patched.