VMware vCenter Vulnerability CVE-2026-123890
How to Check Exposure and Update to 8.0 U3m / 9.x
CVE-2026-123890: a CVSS 9.8 vCenter auth bypass, reportedly exploited since September. Update to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200; no workaround. Fixes.
On November 19, 2026, Broadcom published advisory VMSA-2026-0009, which includes CVE-2026-123890, an authentication bypass in the VMware Directory Service (vmdir) of VMware vCenter Server. An attacker who can reach vCenter over the network can sign in as an administrator without a password. The CVSS 3.1 score is 9.8 (Critical), and Broadcom lists no workaround. Google's Mandiant and GTIG report that a suspected China-nexus espionage group exploited it as a zero-day from early September 2026. The only fix is to update to vCenter 9.1.1.0200, 9.0.2.0200, 8.0 U3m, or VCF 5.2.5.
This article is based on Broadcom's advisory (VMSA-2026-0009.1) and FAQ, Google's threat intelligence blog, and Rapid7's write-up as of November 20, 2026. Where we could not confirm something, we say so. For other vulnerabilities of the same day, see the November 20 vulnerability digest.
Key points in three lines
- What happened: The VMware Directory Service in vCenter has an authentication bypass that lets an attacker with network access sign in as administrator@vsphere.local without a password (CVE-2026-123890, CVSS 3.1 9.8). Google's analysis says the entry point is an RPC interface on TCP port 2012.
- Who is affected: Broadcom lists fixes for vCenter 9.1.x, 9.0.x and 8.0, VCF 5.x and Telco Cloud products. vCenter 7.0 has no published fix; extended-support customers are told to contact Broadcom Support. ESX hosts are stated as not affected.
- What to do: Update to 9.1.1.0200 / 9.0.2.0200 / 8.0 U3m / VCF 5.2.5. Broadcom says there is no workaround and treats it as an emergency change. In parallel, check for signs of abuse (unknown SSO administrators, SSH enable records in VAMI, and so on).
Affected scope at a glance
These are the vCenter fixes listed in VMSA-2026-0009 (revision of 2026-11-20). Build numbers are not given in the advisory or the FAQ, so this article does not state them.
| Environment | Affected versions | Fixed version |
|---|---|---|
| vCenter in VCF / vSphere Foundation 9.1 | 9.1.x | 9.1.1.0200 |
| vCenter in VCF / vSphere Foundation 9.0 | 9.0.x | 9.0.2.0200 |
| vCenter Server 8.0 | 8.0 | 8.0 U3m |
| vCenter Server 7.0 | 7.0 (stated as affected in the FAQ) | No published fix; extended-support customers contact Broadcom Support |
| VMware Cloud Foundation 5.x | 5.x | 5.2.5 (async patch, KB 88287) |
| Telco Cloud Platform / Infrastructure | Listed versions | See KB 463116 |
| vSphere 6.5 / 6.7 | FAQ says to presume affected | No fix (end of support) |
| ESX hosts | Not affected | Not needed |
The same advisory also covers CVE-2026-123891 to 123893 (SDDC Manager, CVSS 8.1, 7.2, 6.7) and CVE-2026-123894 (SAML token signature bypass in VMware Tools for Windows, CVSS 6.7). Broadcom's advisory does not mention exploitation of these four, and all require an authenticated attacker or local privileges. SDDC Manager is fixed in 9.1.1.0200 / 9.0.2.0100 / 5.2.5, and VMware Tools in 13.1.5.0 / 12.5.5. This article focuses on CVE-2026-123890 in vCenter.
What is happening, in plain terms
vCenter is the control tower that manages your virtual machines. Its VMware Directory Service (vmdir) holds the directory of users and permissions used for single sign-on (SSO). CVE-2026-123890 is a flaw in the authentication procedure of this directory: an attacker is treated as an administrator without knowing the password. Broadcom's advisory describes the attack vector as a malicious actor with network access bypassing authentication.
Google's technical analysis says the flaw is in vmdir's DCE/RPC interface. The SRP (a password authentication scheme) handling that listens on TCP port 2012 relies on identifiers built from predictable timestamps, so the session key used mid-authentication can be extracted without authentication. The result is access as administrator@vsphere.local. CVE-2026-59309, fixed in July, is a different flaw in LDAP (ports 389/636) authorization tokens. Per Rapid7, vCenter systems that already received the July fix still need this update.
Google also describes real-world abuse in detail. The attackers first entered through another vulnerability in a BeyondTrust remote support appliance, then attacked vCenter from an internal Linux appliance. After gaining vCenter administrator rights they stole the SSO signing key to impersonate any user (forged SAML tokens), briefly enabled SSH through VAMI (the vCenter management interface) to take cryptographic keys and the database password, then reached ESXi hosts and extracted Active Directory data from virtual machine disks. That is why you need to check whether you have already been compromised, not just update.
Severity and exploitation status
Broadcom's advisory rates it 9.8 (Critical) on CVSS 3.1. According to Rapid7 the vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H and the weakness class is CWE-288. That means network-reachable, no authentication, no user interaction, and high impact on confidentiality, integrity and availability.
Sources differ on exploitation. Broadcom's advisory itself does not state whether it is exploited (it only describes the attack vector). Google's Mandiant and GTIG, however, report that a suspected China-nexus espionage group, ARMORY CASTLE (formerly UNC5221), exploited it as a zero-day from early September 2026, based on forensic evidence. We could not find it in CISA's KEV catalog when we checked its search page on November 20, 2026 (the result view was partial, so we cannot say it is absent). We could not confirm the existence of public proof-of-concept code.
How to check whether you are affected
Step 1: Check the vCenter version. In the vSphere Client, select the vCenter and look at the version and build on the Summary tab. The VAMI summary (https://<vCenter address>:5480) also shows the version. With PowerCLI you can use the method in Broadcom's FAQ.
# After connecting to vCenter with PowerCLI
$global:DefaultVIServer.Version
$global:DefaultVIServer.BuildCompare the result with the table above. 9.1.x below 9.1.1.0200, 9.0.x below 9.0.2.0200, and 8.0 below U3m need the update. Check every vCenter, including ones in an Enhanced Linked Mode setup.
Step 2: Check where the vmdir port (TCP 2012) is reachable from. Google's analysis names port 2012 as the entry point. Test from a management workstation and from other internal networks (run this only against your own vCenter).
# From a management host or a server in another segment (your own vCenter only)
nmap -Pn -p 2012,389,636,443,5480 <vCenter address>
# In the appliance shell on vCenter, check what is listening
ss -tlnp | grep -E ':(2012|389|636)\b'If the port shows open for networks wider than your intended management range, review that range. This is not a substitute for updating; Broadcom lists no workaround.
Step 3: Look for signs of compromise. Below are traces from Google's report that a small-business administrator can check relatively easily. Finding one does not prove a breach, but if you find any, update urgently and consult Broadcom Support or a specialist.
- Unfamiliar administrator accounts in vCenter SSO (vSphere Client, Administration > Single Sign On > Users and Groups). Google cites a local administrator whose name starts with sps- created by the attacker
- VAMI logs showing SSH enabled and then disabled shortly after (Google cites PUT /rest/appliance/access/ssh on TCP 5480)
- The files /tmp/123, /tmp/sss, /tmp/dbr or /usr/bin/vmtoolscs on vCenter or internal Linux appliances
- SSH servers on high ports announcing the banner SSH-2.0-pulsesecure_23345
- Traffic with these IP addresses, which Google lists as a suspected obfuscation network: 103.147.251.5, 103.190.38.3, 118.174.128.34, 118.174.128.36, 118.174.128.38, 176.9.89.66, 185.71.15.109, 220.121.128.41, 222.108.77.44, 61.216.56.127, 81.45.89.43
# In the vCenter appliance shell (checking file names listed by Google)
ls -l /tmp/123 /tmp/sss /tmp/dbr /usr/bin/vmtoolscs 2>/dev/null
systemctl list-units --all | grep -i vmtoolscs
# On ESXi hosts, check root's public keys for unknown entries (Google observed a key being added)
cat /etc/ssh/keys-root/authorized_keysWhat to do by environment
vCenter 9.1 (VCF / vSphere Foundation)
Update to 9.1.1.0200. Versions of 9.1.x earlier than 9.1.1.0200 are affected. Update through VAMI or the standard procedure; Quick Patch is not eligible.
vCenter 9.0 (VCF / vSphere Foundation)
Update to 9.0.2.0200. One caveat: Broadcom explains that applying 9.0.2.0200 or 8.0 U3m blocks a direct upgrade to VCF 9.1.1 (a Back-in-Time restriction). Organizations in the middle of a move to 9.1 must wait for VCF 9.1.2 or upgrade vCenter to 9.1.1 first. See Broadcom KB 67077 and the FAQ.
vCenter 8.0
Update to 8.0 U3m. 8.0 U3m is named as the fixed release for the 8.0 line. Check Broadcom's techdocs release notes for details, including build numbers.
vCenter 7.0 (end of support, extended support)
vSphere 7 reached end of general support on October 2, 2025 (Broadcom FAQ). The advisory has no fix for 7.0 and says customers with extended support should request one from Broadcom Support. Without an extended-support contract, presume 7.0 (and 6.5 / 6.7) is affected, assume no fix will come, and plan the move to current VCF 9.1. Until then, apply the mitigations below as far as you can and prioritize checking for signs of compromise.
VMware Cloud Foundation 5.x
Apply the VCF 5.2.5 async patch (KB 88287). It applies vCenter 8.0 U3m, and the SDDC Manager fixes (5.2.5) are covered at the same time.
Before you update
Broadcom's FAQ has no snapshot or backup procedure. The following is general practice, not an instruction from the advisory. Before updating vCenter, take a backup of vCenter itself (VAMI file-based backup) and a snapshot of the virtual appliance so you can roll back. In a linked configuration, snapshot all vCenters in the same window. Broadcom explains that the vSphere Client is temporarily unavailable during the update but running virtual machines keep running; however, KMS-backed encryption operations are unavailable while vCenter is down.
Note that if you suspect you are already compromised, updating alone is not enough. If the attacker stole the SSO signing key, forged tokens might keep working after the update. Cyber Kendra recommends rotating the SSO signing certificate and credentials, but Google's post does not say so. Decide the procedure with Broadcom Support or a specialist.
Mitigations while you cannot patch
Broadcom states there is no workaround for this vulnerability. The following is not a fix; it only helps reduce exposure until you update.
- Make sure vCenter is not directly reachable from the internet (top priority if it is exposed)
- Separate the management network and restrict traffic to vCenter (especially TCP 2012, 443, 5480 and 22) to management workstations and required systems. Google's VCSA Hardening & Logging Tool (GitHub: mandiant/vcsa-hardening-tool) includes firewall rules that drop port 2012 from non-allowlisted addresses. Blocking 2012 might affect other vCenter functions, which we could not confirm, so test and follow change control before production
- Restrict outbound traffic from vCenter (Google says this helps against data exfiltration and Slack-based remote control)
- If you use BeyondTrust remote support products, confirm the fix for CVE-2026-102764 (BT26-05) is applied
Timeline
| Date | Event |
|---|---|
| 2026-07-29 | A different vCenter authentication bypass, CVE-2026-59309, is published in VMSA-2026-0006 (per Google's post) |
| Early 2026-09 | ARMORY CASTLE exploits CVE-2026-123890 as a zero-day (per Google's forensic evidence) |
| 2026-10-15 | Google reports the same group's exploitation of BeyondTrust in a separate post (same) |
| 2026-11-19 | Broadcom publishes VMSA-2026-0009 |
| 2026-11-20 | Broadcom updates to VMSA-2026-0009.1 (clarifies affected VMware Tools versions). Google publishes its ARMORY CASTLE write-up |
Today's checklist
- Inventory all your vCenters (production, test, and every linked instance) and confirm their versions
- If affected, decide which of 9.1.1.0200 / 9.0.2.0200 / 8.0 U3m / VCF 5.2.5 to move to, and schedule it as an emergency change per Broadcom
- Take a vCenter backup and snapshot before updating (all instances in the same window)
- Confirm vCenter is not reachable from the internet or broad networks (reach of TCP 2012, 443, 5480, 22)
- Check SSO administrator accounts for unfamiliar entries
- Check VAMI logs for SSH enable/disable records
- If you run 7.0 / 6.x, check whether you have extended support and draft a migration plan
- Check the update status of remote support products such as BeyondTrust that serve as entry points
- After updating, confirm the version is the fixed one and that you can sign in to the management interface
For the overall approach to patching, see the SMB patch and update management guide. For what an outside review costs, see vulnerability assessment costs.
Frequently asked questions
Do I still need to update if vCenter is internal-only and not exposed to the internet?
Yes. The flaw can be exploited by anyone who can reach vCenter over the network. In the case Google reported, the attackers first entered through another device and then attacked the internal vCenter. Not being exposed to the internet lowers risk but does not remove the need to update.
Is a vCenter that received the July CVE-2026-59309 fix safe?
No. CVE-2026-59309 is an LDAP authorization token issue, and CVE-2026-123890 is a different flaw. Rapid7, citing Broadcom's FAQ, says environments with the July fix still need this update. Google's post also says the attack was run against a vCenter already patched for the July flaw.
If I was already compromised, does updating restore a clean state?
Not necessarily. In Google's report the attackers used tooling that steals the SSO signing key and forges tokens to impersonate any user, so suspicious accounts or settings can remain after the update. If you find signs, consult Broadcom Support or a specialist.
What should I do if I run vCenter 7.0 without extended support?
The advisory has no fix for 7.0, and the FAQ only directs extended-support customers to Broadcom Support. Without a contract you cannot expect an official fix. Reduce exposure by separating the management network and restricting traffic, check for signs of compromise, and move quickly to a supported version.
Sources
- Broadcom VMSA-2026-0009 (vCenter, Tools and SDDC Manager updates)
- VMSA-2026-0009 FAQ (GitHub: vmware/vcf-security-and-compliance-guidelines)
- Google Cloud Threat Intelligence: ARMORY CASTLE Exploits vSphere
- Rapid7: CVE-2026-123890 Critical Authentication Bypass in VMware vCenter
- Cyber Kendra: Chinese Hackers Exploited vCenter Zero-Day CVE-2026-123890
- CISA Known Exploited Vulnerabilities Catalog
- Mandiant VCSA Hardening & Logging Tool (GitHub)
株式会社オブライト
Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.
Related free tools (no sign-up, instant results)
Feel free to contact us
Contact Us