- Plain-language security guides for Central Florida businesses/
- News/
- VMware vCenter Update: What to Ask Whoever Runs Your Servers/
VMware vCenter Update: What to Ask Whoever Runs Your Servers

Table of Contents
What happened #
The notice rates the update “critical” and treats the vCenter flaw as an emergency. It says someone who can reach vCenter over the network could get in without a password. The notes list no workaround, so the fix is the update. The same notice also fixes four smaller problems in other VMware parts.
The report says a hacking group it suspects is tied to China used this flaw more than two months before the fix existed. In the case it describes, the group had already got into the victim’s network by another route.
The report says the group used the flaw to make itself an administrator and to copy vCenter’s stored login records. It then made fake sign-in passes that skip the second step of sign-in. It switched on a remote login feature, used it, and switched it off again. It also copied files out of virtual machines, including what look like the files Windows uses to store account logins.
What this means for a business owner #
Most small offices do not run vCenter. It is used where a company, or a provider working for it, runs a group of virtual servers. If your servers sit in a closet, a data center or a provider’s private cloud, ask.
An earlier update does not cover this one. The report says this is a different flaw from the vCenter flaws fixed in late July. The notice calls it “new and distinct”, so the update has to be installed again.
Older versions are a problem. The notice says version 7 stopped getting general support on October 2, 2025. Fixes for it go only to customers with an extended support contract, and versions the notice does not list should be treated as affected. The report says the attack tool works on versions 7 and 8.
An update does not prove nobody got in first. The report says the group deleted its own tools after using them. A clean check is good news, but it is not proof.
What we do not know #
How many organizations were hit. The report describes one break-in and gives no count. We found no public count.
Whether anyone else is using the flaw. The report names one group. The notice we read does not mention attacks.
Whether your own systems are affected. That depends on the version you run. Your IT person or provider can tell you.
Five questions to ask this week #
- Do we run VMware vCenter, ourselves or through a provider, and who is responsible for updating it?
- Has it been updated to a fixed version since November 19? Please answer in writing, with the version. An update from the summer does not count.
- Who can reach the vCenter management pages over the network? The report advises blocking everything by default and allowing only the few computers that need access. In the case it describes, the group was already inside the network, so everyday office computers should not be on that list.
- After the update, did anyone look for signs it was entered earlier? The report describes administrator accounts nobody recognizes and remote login switched on without a request. Ask for a written answer.
- If we run version 7, do we have an extended support contract, or a date for moving off it?
These questions will not prevent an attack. The update is the fix.
If you think someone got in #
Call your IT person or provider right away. Ask them to keep every log and record before they change anything, because the group removed its own tools.
Take this to your next IT meeting #
Send the five questions today and ask for written answers. If you are not sure whether vCenter is part of your business, that is the first thing to find out.
If your IT person wants to search for the signs the report published, we collected them in an open repository, with sources and a hunting guide: VMware vCenter indicators on GitHub. It is not tested, and it will go stale, so check the dates in it.
At SOC-Lite, a named analyst reviews your alerts, calls you when one is real, works with your IT person or MSP on the fix, and keeps the evidence. A visibility check is free, it takes 20 minutes, and you talk to us by phone or at your office. Book a visibility check
Updates #
2026-11-19: First published, based on the sources below as of this date.
2026-11-19: Added a link to our open repository of the report’s indicators.
Sources #
- Broadcom (VMware), VMSA-2026-0009 questions and answers: critical rating, emergency change, the five issues (CVE-2026-123890 to CVE-2026-123894), no workaround as listed, “new and distinct”, vSphere 7 support.
- VMware Security Blog, advisory list: the advisory title and publication date, November 19, 2026.
- SOC-Lite by BansalAI, VMware vCenter indicators: our own collection of the indicators the report published and a hunting guide, with the source it draws on.
- Google Threat Intelligence Group and Mandiant, ARMORY CASTLE Exploits vSphere: early September use, what the group did, the tools it removed, the hardening advice, versions 7 and 8.