Menu
VULNERABILITIES & FIXES

VMware vCenter Authentication Bypass CVE-2026-123890: Critical Flaw, Fixed Versions and Upgrade Risks

Uday Patil Nov 19, 2026 5 min read 9 views
VMware vCenter Authentication Bypass CVE-2026-123890: Critical Flaw, Fixed Versions and Upgrade Risks

Broadcom released a fix on November 19, 2026, for a critical VMware vCenter authentication bypass that attackers had already used. Mandiant found forensic evidence that the threat group ARMORY CASTLE exploited CVE-2026-123890 in early September, gaining administrative access to an internal vCenter server.

Broadcom rates the flaw 9.8 out of 10 and lists no workaround. Administrators can use the fixed-version table to identify their patch. Teams migrating to VMware Cloud Foundation (VCF) 9.1.1 should also check the upgrade sequence before installing it.

What happened in the September vCenter attack?

The vulnerability affects VMware Directory Service, part of vCenter’s identity infrastructure. An attacker who can reach the affected service over the network can bypass authentication without an existing account. That matters even when vCenter is accessible only from inside an organization’s network.

In their November 19 investigation, Mandiant and Google Threat Intelligence Group described an intrusion in which ARMORY CASTLE targeted an internal vCenter server and created a vSphere Single Sign-On administrator account. Investigators traced exploitation to early September, more than two months before public disclosure.

For a security team responding now, the patch date and the exposure window answer different questions. Verify the running build to establish whether the fix is in place. To investigate earlier access, review available identity and administrative records for unexpected privileged accounts or permission changes while the appliance was vulnerable.

Which vCenter versions fix CVE-2026-123890?

Use the row for your product and release line. Broadcom lists a separate procedure for Cloud Foundation 5.x and directs vCenter 7.0 customers with extended support to contact its support team.

Product or environmentRelease lineFixed version or next action
VMware Cloud Foundation or vSphere FoundationvCenter 9.1.x9.1.1.0200
VMware Cloud Foundation or vSphere FoundationvCenter 9.0.x9.0.2.0200
VMware vCenter8.08.0 Update 3m
VMware Cloud Foundation5.x5.2.5. Follow Broadcom’s asynchronous patching guidance.
VMware vCenter7.0Contact Broadcom Support if your deployment has an eligible extended support contract.
VMware Telco Cloud Platform or Telco Cloud InfrastructureProduct versions listed in the advisoryFollow KB463116, linked from the Telco rows in Broadcom’s response matrix.

Check your product in Broadcom’s official response matrix for the applicable release notes and patch instructions.

Planning a VCF 9.1.1 upgrade? Check the patch order

Installing vCenter 8.0 Update 3m or 9.0.2.0200 can block a subsequent upgrade to VCF 9.1.1. Broadcom calls this a “back-in-time” restriction: the patched source build is newer than the build in the intended upgrade target.

If your migration is already underway, check whether your deployment supports moving to the 9.1.1 release line first and then applying its security update. Before changing an approved maintenance plan, compare your exact source build and target release with Broadcom’s upgrade guidance for this advisory.

What else does VMSA-2026-0009 fix?

The advisory covers five vulnerabilities. The September exploitation documented by Mandiant concerns the vCenter flaw. The other four affect SDDC Manager, VCF Installer or VMware Tools for Windows and have different access requirements.

CVEComponentImpact and required accessBroadcom CVSS v3 score
CVE-2026-123890vCenterAuthentication bypass by an attacker with network access to the affected service.9.8
CVE-2026-123891SDDC ManagerAn authenticated attacker can use SQL injection to read or modify database records.8.1
CVE-2026-123892SDDC ManagerAn authenticated attacker can use command injection to run commands on the appliance.7.2
CVE-2026-123893SDDC Manager or VCF InstallerA local attacker with administrative access can elevate privileges to root.6.7
CVE-2026-123894VMware Tools for WindowsA local privileged process can gain additional privileges inside a Windows guest configured with Guest Alias mapping.6.7

SDDC Manager has its own fixed builds

On the 9.0 branch, the version numbers differ by component: Broadcom lists 9.0.2.0200 for vCenter and 9.0.2.0100 for SDDC Manager. Check each component’s installed version separately before closing the change ticket.

SDDC Manager release lineCumulative update listed on November 19
9.1.x9.1.1.0200
9.0.x9.0.2.0100
VCF 5.x5.2.5

For teams reviewing older change records, Broadcom says the two injection flaws were first addressed in SDDC Manager 9.1.0.0. The local privilege-escalation fix followed in 9.1.1.0. The 9.1.1.0200 cumulative update includes all three.

VMware Tools for Windows needs a guest-level check

For CVE-2026-123894, Broadcom lists VMware Tools 13.1.5.0 for the 13.x branch and 12.5.5 for the applicable older Windows releases in its matrix. The 12.5.5 package includes 12.4.10 for 32-bit Windows. Check the installed Tools version in each Windows VM’s Summary view. Guest Alias mapping is a separate configuration check.

How to verify the update and plan the maintenance window

In the vSphere Client, select the vCenter instance and check its version and build in the Summary tab. If you use PowerCLI with a default vCenter connection, you can inspect that connection with:

$global:DefaultVIServer.Version
$global:DefaultVIServer.Build

Record the instance name alongside the build so the result can be matched to the correct appliance. Repeat the check after patching. Inventory SDDC Manager and Windows guest Tools separately wherever those components are deployed.

Broadcom says these fixes require a standard update method. vCenter Quick Patch is unavailable for this advisory. While arranging the update, limit management-service access to the networks and systems that need it. Broadcom lists no official workaround.

Will running virtual machines shut down during the vCenter update?

According to Broadcom’s maintenance FAQ, running virtual machines and container workloads continue operating while vCenter is updated. The vSphere Client and other management interfaces are temporarily unavailable. Existing encrypted workloads, vSphere High Availability and vSAN continue operating, although some new encryption requests and key rotations may need to wait until vCenter returns.

For the change ticket, record which management functions will be unavailable, who will verify the running build afterward, and whether any scheduled encryption or key-management work overlaps the maintenance window.

Official sources and related coverage

Correction, November 20, 2026: An earlier version of this article said exploitation of CVE-2026-123890 had not been confirmed. Mandiant and Google Threat Intelligence Group documented its use in an intrusion in early September 2026.

Uday Patil
About The Author

Uday Patil

Uday Patil is a Cybersecurity Researcher, DevSecOps Engineer, and the Founder of CyberUpdates365. Specializing in Threat Intelligence and Zero-Day vulnerability analysis, Uday is dedicated to breaking down complex cyber threats into actionable insights. His mission is to empower developers, security teams, and aspiring tech talent with rapid alerts, practical guidance, and career mentorship.