VMware vCenter bug lets anyone on the network in without a password. Update to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200 (CVE-2026-123890)

5 min read

How to fix CVE-2026-123890: upgrade vCenter to 8.0 U3m, 9.0.2.0200, 9.1.1.0200 or VCF 5.2.5. Broadcom's VMSA-2026-0009 fixes a CVSS 9.8 login bypass in the vCenter Directory Service with no workaround, plus four SDDC Manager and VMware Tools bugs.

BREAKING: VMware vCenter bug lets anyone on the network in without a password. Update to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200 (CVE-2026-123890)
On this page

Broadcom shipped an emergency fix on November 19, 2026 for CVE-2026-123890, a bug in VMware vCenter that lets anyone who can reach vCenter over the network get in without a password. vCenter is the console that runs a company's whole VMware estate: every host, every virtual machine, every snapshot. Getting into it is close to getting into everything it manages.

The advisory, VMSA-2026-0009, rates it Critical (CVSS 9.8) and lists no workaround. Broadcom's own FAQ calls the vCenter fix an emergency change. Mandiant reported the bug. This post covers which build fixes your version, what to do about vCenter 7.0, and what to lock down while you schedule the update.

How to fix

Update vCenter to the fixed build for your line. Patches are cumulative, so anything newer also fixes it:

  • vCenter 9.1.x (VCF and vSphere Foundation 9.1): 9.1.1.0200
  • vCenter 9.0.x (VCF and vSphere Foundation 9.0): 9.0.2.0200
  • vCenter 8.0: 8.0 U3m
  • VMware Cloud Foundation 5.x: 5.2.5, applying vCenter 8.0 U3m through the async patching process in KB 88287
  • Telco Cloud Platform 3.0 to 5.2 and Telco Cloud Infrastructure 3.0: follow KB463116
  • vCenter 7.0: no public patch. Broadcom says to presume 7.0 is affected; customers with an extended support contract can request a fix through that channel. Everyone else needs a plan to move to 8.0 U3m or 9.x.

To see what you run, open the vSphere Client and check the vCenter Summary tab, or after Connect-VIServer in PowerCLI read $global:DefaultVIServer.Version and $global:DefaultVIServer.Build. The update can go through the vCenter appliance management page (VAMI). It is not eligible for vCenter Quick Patch.

Updating vCenter does not stop running virtual machines. You lose the vSphere Client for the length of the update, and new encryption operations against a standard key provider pause until vCenter is back. ESX hosts do not need an update for this advisory.

What the bug does

The flaw is in the VMware Directory Service, the part of vCenter that holds its single sign-on accounts. Broadcom's description is short: an attacker with network access to vCenter can bypass authentication and gain unauthorized access. No account, no click from an admin, and no special configuration are needed. Enhanced Linked Mode makes no difference; the FAQ says the bug is present either way.

Broadcom says this is a new bug, separate from CVE-2026-59309, the Directory Service bypass it fixed in July in VMSA-2026-0006. If you patched for that one, you still need this update.

The same directory service has been a target before. Mandiant found that a China-linked espionage group, UNC3886, exploited an earlier bug in it (CVE-2023-34048) for about a year and a half before it was public. That history is why a Directory Service bug reported by Mandiant deserves fast handling, even though nobody has reported attacks on this one.

Who is exposed

Every vCenter below the fixed builds, standalone or inside VMware Cloud Foundation, vSphere Foundation or the Telco Cloud products. The real question is who can reach it. Most vCenter servers sit on a management network, which keeps random internet scanners away but does nothing against someone who already has a foothold inside, such as a phished laptop or a compromised VPN account.

While the update is scheduled:

  • Confirm vCenter is not reachable from the internet. Check firewall and load balancer rules, not just the design diagram.
  • Limit who can reach it on the inside to admin jump hosts and the systems that need it (backup, monitoring, automation).
  • Watch vCenter sign-in and SSO logs for logins you can't explain, and for new local accounts or role changes.

Broadcom is clear that these are compensating controls, not workarounds. The update is the fix.

The rest of VMSA-2026-0009

  • CVE-2026-123891 (CVSS 8.1): SQL injection in SDDC Manager that lets a signed-in user read and write its database.
  • CVE-2026-123892 (CVSS 7.2): command injection in SDDC Manager for a signed-in user.
  • CVE-2026-123893 (CVSS 6.7): an SDDC Manager admin can become root on the appliance.
  • SDDC Manager fixes: 9.1.1.0200, 9.0.2.0100 and 5.2.5. If you are already on SDDC Manager 9.1.1.0, those three are already fixed.
  • CVE-2026-123894 (CVSS 6.7): a SAML token signature bypass in VMware Tools for Windows. Someone who already controls a privileged process inside a Windows VM that uses guest alias mapping can raise their rights inside that VM. Fixed in VMware Tools 13.1.5.0 and 12.5.5. It is not a VM escape, and turning off guest operations does not protect against it.

ESX, NSX, VCF Operations, VCF Automation, Workstation and Fusion are not affected.

What this is not

As of the morning of November 19, Broadcom has not reported exploitation, CISA has not added the CVE to its Known Exploited Vulnerabilities list, and there is no public exploit. vCenter bugs have been added to that list many times before, so check again before you decide this can wait for the next maintenance window.

What do people ask about the vCenter CVE-2026-123890 fix?

Do I need to patch ESX hosts?

No. Broadcom's FAQ says ESX is not affected by this advisory. Update vCenter, SDDC Manager if you run VCF, and VMware Tools in Windows VMs.

We patched in July for CVE-2026-59309. Are we covered?

No. CVE-2026-123890 is a different bug. You need 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5.

Is there a workaround?

Broadcom lists none. Tight network access to vCenter reduces who can try, but only the update closes the hole.

What about vCenter 7.0?

vSphere 7 left general support on October 2, 2025. Broadcom says to presume it is affected and has no public patch. With extended support, request one; without it, plan the move to 8.0 U3m or 9.x and keep 7.0 vCenter servers tightly fenced off until then.

Will updating vCenter take down my VMs?

No. Workloads keep running. You lose management access briefly while vCenter restarts.

If AI agents or automation scripts in your team hold vCenter credentials or run infrastructure commands, check if your agents touch this product with HOL Guard. Every advisory we track is in the HOL Guard CVE index.

References

All articles

Keep exploring

The engineering desk continues across the ecosystem: security research on shipping agents safely, and plugins that put the standards to work.