VMware vCenter zero-day CVE-2026-123890: what to do now

Broadcom patched a vCenter login bypass on November 19, 2026, after attacks since September. What small businesses running VMware servers should do today.

Book a visit or pickup (213) 986-4855

On November 19, 2026, Broadcom released an emergency update for VMware vCenter, the console used to manage VMware servers and the virtual machines running on them. The flaw, CVE-2026-123890, lets an attacker with network access get into vCenter without a password. Google's Mandiant team, which reported it, says a China-linked espionage group had been exploiting it since early September, and on November 20 CISA added it to its catalog of vulnerabilities known to be exploited. If your business runs its own VMware servers, this is a patch for today.

A technician's hands working on a circuit board on a repair bench

What was announced

Why it matters even if you are not a target for spies

Espionage groups tend to go first, but once a technique is known, criminal gangs follow. vCenter is a particularly valuable target: whoever controls it controls every virtual server you run, and often the backups of those servers too. In the attacks described by Mandiant, the intruders created administrator accounts and moved from vCenter to the underlying ESXi hosts. Ransomware gangs have used the same path in the past to encrypt whole virtual environments at once.

Many small offices run a single VMware host with a handful of virtual machines (a file server, an accounting application, a domain controller) and vCenter was set up years ago by whoever installed it. That is exactly the kind of system that misses an emergency patch.

What to do now

  1. Check whether you run vCenter and which version. Your IT provider can tell you in minutes. If you only have a free standalone ESXi host with no vCenter, this particular flaw does not apply, but keep ESXi up to date as well.
  2. Patch to the fixed version for your branch, after making sure you have a recent, working backup of the vCenter appliance.
  3. If you are still on vCenter 7.0, treat the upgrade as urgent. Until then, make sure vCenter can only be reached from a small management network, never from the internet or from the general office network.
  4. Look for signs of compromise. Ask your provider to review vCenter for administrator accounts nobody recognizes, unexpected logins and changes to ESXi hosts. Mandiant advises examining systems for evidence of compromise, not just patching.
  5. Protect the backups. Make sure at least one copy of your virtual machine backups cannot be changed or deleted using vCenter or domain credentials.

Sources

How we can help

Through our managed IT services we can check your VMware version, apply the update and review the system for warning signs. If virtual machines have already been encrypted or damaged, see our page on virtual machine and backup recovery. Call (213) 986-4855.

Call us Book a visit