Skip to content

A VMware vCenter Flaw Opens Your Company's Servers Without a Password: Exploited Since September, and Patching Alone Is Not Enough

Short answer

Broadcom issued an emergency fix for a VMware vCenter flaw scored 9.8 that gives attackers admin rights without a password, exploited since September. Find your version, the fixed one, and 5 steps after patching.

Origami Team

Editorial Team · · 6 min read

Share on WhatsApp
Like what we publish? Pin Origami as a preferred source on Google.Add as a preferred source on Google
A VMware vCenter Flaw Opens Your Company's Servers Without a Password: Exploited Since September, and Patching Alone Is Not Enough

If your company's servers run on VMware and are managed from vCenter, update it today. On 19 November 2026 Broadcom released an emergency fix for a vCenter flaw scored 9.8 out of 10 that lets anyone who can reach vCenter over the network skip the login and get administrator rights. There is no workaround. Google and Mandiant say attackers have been exploiting it since early September 2026, more than two months before the fix. You need three steps: install the fixed version, restrict who can reach vCenter, then check whether anyone got in before you patched.

What exactly happened?

Broadcom published security advisory VMSA-2026-0009, rated Critical. It fixes 5 flaws scored between 6.7 and 9.8. The worst, CVE-2026-123890, sits in vCenter's directory service. The advisory says an attacker with network access to vCenter can bypass authentication and gain unauthorised access, and the workaround field reads simply «None».

Broadcom credits Mandiant with reporting the flaw. The same day, Google Threat Intelligence published a report saying a group it calls ARMORY CASTLE exploited it in early September 2026 with a tool named BONESAW, which works against vCenter 7 and 8 appliances.

Why vCenter is so dangerous for your company

vCenter is the console that controls all your virtual servers: email, accounting, file servers and databases. Whoever holds administrator rights on it effectively holds everything running underneath. Google's report describes exactly that:

  • The flaw gives the attacker a session as the main administrator account, administrator@vsphere.local.
  • The attackers created a new administrator account, switched SSH on and then off again to cover their tracks.
  • They stole the login signing key, which let them forge any user's identity and bypass two-factor authentication.
  • They read a virtual server's disk from outside and pulled out NTDS files, which hold the staff account data for the network.

Put simply: the attacker needs nobody's password and never passes through the security software on staff computers.

Which version does your server need?

Ask your IT lead to open the Summary tab in the vSphere Client to see the vCenter version, then compare it with this table from Broadcom's advisory:

Your vCenter versionFixed version
9.19.1.1.0200
9.09.0.2.0200
8.08.0 U3m
VMware Cloud Foundation 5.x5.2.5
7.0No public fix, only for customers with an extended support contract

Watch out for version 7: its general support ended on 2 October 2025, and Broadcom says older versions such as 6.5 and 6.7 should be presumed affected. Broadcom confirms that updating vCenter does not stop running virtual servers, only the management console goes down for a few minutes, and that the ESX hosts themselves need no update for this advisory. VMware Tools inside Windows servers does need updating to 13.1.5.0 or 12.5.5 because of another flaw in the same advisory.

Why patching alone is not enough

Because exploitation started more than two months before the fix. If your vCenter was exposed during that time, the update closes the door but does not throw out anyone already inside. So:

  1. Install the fixed version in the nearest maintenance window, and treat it as the emergency change Broadcom says it is.
  2. Restrict access to vCenter: it must never be reachable from the internet, and only the IT team's machines need to reach it. Mandiant recommends a default-deny firewall policy that allows only the ports needed, such as 443 and 5480, and has published a free tool to harden vCenter and log its commands.
  3. Review administrator accounts: look for any vsphere.local administrator your team does not recognise, and for SSH switched on without a request.
  4. Check the published indicators: Google's report lists IP addresses, file names and YARA rules your team or provider can compare with your logs.
  5. Change sensitive passwords if you find a trace, starting with network administrator accounts, because NTDS files were a target.

If your environment is an engineered system such as VxRail or SimpliVity, Broadcom says to wait for that vendor's guidance rather than apply the update directly.

The Origami view

In many mid-sized companies we see a vCenter installed once and not updated for years, because the servers work and nobody wants to touch them. This flaw shows the cost of that: one outdated console is enough to open every system. Attacks on virtual infrastructure often come before ransomware, as we explained in our article on ransomware protection.

Our advice: give every management system in your company, such as vCenter, the firewall and backups, a clear owner and a monthly update date, and separate it from the staff network. If you need someone to review your vCenter setup or plan the update, the Origami team can help.

Conclusion

If your company uses VMware: find your vCenter version today, install the fixed version this week, block any access to it from outside the IT team, then check accounts and logs for earlier intrusion. And if you are on version 7 without an extended support contract, an upgrade plan is no longer something to postpone.

  • #VMware
  • #vCenter vulnerability
  • #Cybersecurity
  • #Security updates
  • #Virtualization

Frequently asked questions

How do I know if my company uses vCenter?

Ask your IT lead whether your servers run on VMware vSphere and are managed from a single console. If so, that console is vCenter, and its version appears on the Summary tab of the vSphere Client.

Will our servers stop during the update?

No. Broadcom says virtual servers keep running and only the management console is unavailable for a few minutes, so the update fits a short maintenance window.

Is there a workaround if I cannot update right now?

Broadcom lists no official workaround. The most you can do until you update is block access to vCenter at the firewall except from the IT team's machines.

I updated vCenter. Am I done?

Not necessarily. Exploitation began in early September, so review administrator accounts and SSH status, compare your logs with the indicators in Google's report, and change sensitive passwords if you find a trace.

Have a project in mind?

We build custom systems, apps and websites for your business. Tell us your idea and we will give you a straight answer on it.

See our services

Newsletter

New articles and series, in your inbox.

Follow Origami in Google

Pin Origami as a preferred source and our articles will surface first for you in Google Search and Top Stories.

Add as a preferred source on Google