Security & identity

VMware vCenter CVE-2026-123890: Check If You Are Hit and Patch Now

Broadcom fixed a critical vCenter authentication bypass on 19 Nov 2026. Google says it was exploited since early September. Check exposure, patch, hunt.

By EpiFive Editorial TeamReviewed/updated 8 min readHow we check our guides
On this page

Broadcom released VMSA-2026-0009 on 19 November 2026, fixing CVE-2026-123890, a critical authentication bypass in the VMware Directory Service (vmdird) of vCenter Server. Google Threat Intelligence Group and Mandiant published a report the same day saying an actor they track as ARMORY CASTLE exploited the flaw as a zero-day from early September 2026. If you run vCenter 7.x or 8.x, treat the patch as an emergency change and also check for signs of earlier compromise.

This guide separates what Broadcom said, what Google said, and what is only reported by news outlets. It lists only the indicators Google published, and it does not describe how to exploit the flaw.

What happened

DateEventSource
Early September 2026Google says exploitation of CVE-2026-123890 beganGoogle GTIG and Mandiant report
15 October 2026Earlier Google report on the same actor abusing a BeyondTrust Remote Support flaw (CVE-2026-102764, patched in BT26-05)Google GTIG and Mandiant report
19 November 2026Broadcom publishes VMSA-2026-0009Broadcom FAQ page
19 November 2026Google and Mandiant publish "ARMORY CASTLE Exploits vSphere"Google GTIG and Mandiant report
20 November 2026BleepingComputer reports on the patch and the exploitation claimBleepingComputer

What Broadcom says. VMSA-2026-0009 has an overall severity of Critical and covers five CVEs. Broadcom's FAQ page lists CVE-2026-123890 as an "Authentication bypass in VMware Directory Service; network-reachable" in vCenter. It says Broadcom lists no workarounds and treats the vCenter issue as an ITIL emergency change. The FAQ page we opened does not mention known exploitation. The other four CVEs are CVE-2026-123891, CVE-2026-123892 and CVE-2026-123893 in SDDC Manager, and CVE-2026-123894 in VMware Tools for Windows.

What Google says. Google describes the actor as suspected PRC-nexus. According to Google, it first compromised a BeyondTrust Remote Support appliance, moved to internal Linux systems, and then attacked vCenter. Google describes the flaw as an unauthenticated session key disclosure over DCE/RPC on TCP port 2012 that yields an authenticated session as [email protected]. After that, Google says the actor copied the vmdir database, extracted the SAML signing key, created an SSO administrator account, forged SAML assertions, reached ESXi hosts, and took Active Directory database files from guest VMs.

ClaimWho made itStatus
CVE-2026-123890 was exploited as a zero-day from early September 2026Google GTIG and MandiantNot confirmed on the Broadcom FAQ page; BleepingComputer reports Broadcom has not confirmed it
The actor is suspected PRC-nexusGoogle GTIG and MandiantAttribution is Google's assessment
Number of affected organizationsNobodyUnknown; neither source gives one
How many vCenter servers were compromisedNobodyUnknown

Am I affected?

Per Broadcom's FAQ, affected products are:

ProductAffected?Fixed version named on the FAQ page
vCenter 8.0 (including VCF 5.x)Yes8.0 U3m
vCenter 7.0 and 9.xYesNot stated; read VMSA-2026-0009
vCenter in VCF, VVF, Telco Cloud Platform and InfrastructureYesFollow the VMSA
SDDC Manager 9.1.x, 9.0.x, 5.xYes (three other CVEs)9.1.1.0200, 9.0.2.0100, 5.2.5
VMware Tools for Windows 13.xYes (CVE-2026-123894)13.1.5 (the FAQ lists a trailing ".0" build digit)
VMware Tools for Windows 12.x and 11.xYes12.5.5
ESX, NSX, VCF Operations, VCF AutomationNoNot applicable
vSphere 6.5 and 6.7Presumed affected; Broadcom does not evaluate versions past end of general supportNot listed

Broadcom also says Enhanced Linked Mode is not a mitigation: the vCenter issue exists with or without it. vSphere 7 reached end of general support on 2 October 2025, according to the same FAQ.

Published indicators of compromise

Google published the following. Its full set is in a Google Threat Intelligence collection that needs a registered account; Google states that no hashes or domains are in the blog post. All IP addresses below are labeled by Google as suspected obfuscation network IPs, so they may be shared infrastructure.

TypeIndicator (as published)Description
IP103[.]147[.]251[.]5, 103[.]190[.]38[.]3Suspected obfuscation network
IP118[.]174[.]128[.]34, 118[.]174[.]128[.]36, 118[.]174[.]128[.]38Suspected obfuscation network
IP176[.]9[.]89[.]66, 185[.]71[.]15[.]109, 220[.]121[.]128[.]41Suspected obfuscation network
IP222[.]108[.]77[.]44, 61[.]216[.]56[.]127, 81[.]45[.]89[.]43Suspected obfuscation network
FileActiveSer.jspSLIMSAVAGE web shell
Fileu.jspCAGEMATCH staging web shell
File/tmp/123BONESAW exploit utility
File/tmp/sssSAWSNAKE Golden SAML utility
File/tmp/dbrBEARBONES backdoored SSH server
File/usr/bin/vmtoolscsLAZYBONES backdoor
BannerSSH-2.0-pulsesecure_23345SSH banner on non-standard high ports
Ports53 and 33992BEARBONES listeners (Google example: /tmp/dbr -R -p 53)

Google also lists behaviors to hunt for:

  • Traffic to TCP 2012 from hosts that are not administrative systems.
  • Port scans for 443, 2012, 5480, 9080 and 389 coming from Linux appliances.
  • PUT /rest/appliance/access/ssh on the VAMI (TCP 5480) that enables SSH, followed by SSH logins with a newly created local admin account.
  • Unexpected SSO administrator or machine accounts.
  • A hidden .a directory on a VMFS volume and unexpected entries in the ESXi root authorized_keys.
  • A systemd service that restarts every 50 minutes (LAZYBONES).

Google names SecOps rules including "VMware vCenter VAMI API SSH Enablement", and YARA rules such as G_Hunting_Utility_BONESAW_2, for teams that use those tools.

What to do now

  1. Apply the fixed vCenter version today. For vCenter 8.0, install 8.0 U3m; for 7.x and 9.x, take the fixed version from VMSA-2026-0009, because the FAQ page does not state it. Broadcom calls this an emergency change.
  2. Restrict network access to vCenter now, even before patching. Google recommends allowing only known administrative and backup hosts to reach TCP 443, 2012, 5480 and 22. Broadcom's FAQ says compensating controls are not assessed by Broadcom, so this is a reduction in exposure, not a fix.
  3. Hunt for signs of compromise using the behaviors and indicators above, covering the period from early September 2026 on. Patching does not remove an attacker who already has an SSO admin account or a stolen signing key.
  4. Patch the rest of VMSA-2026-0009 if you use SDDC Manager or VMware Tools for Windows, using the versions in the table above.
  5. Forward logs off the appliance to a SIEM. Google notes that attackers can tamper with local logs.

Step: check the impact of the update

Per Broadcom's FAQ: updating vCenter briefly makes the vSphere Client unavailable, while running VMs and containers continue. Some key management encryption operations, such as new encryption or key rotation, are unavailable while vCenter is offline. SDDC Manager updates do not affect running workloads. The vCenter updates are not eligible for Quick Patch, and the standard update mechanisms, including the VAMI, can apply the patch.

One known issue: Broadcom says upgrades in progress may hit a "Back-in-Time" restriction, and that vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1. It points to KB 67077, and says to wait for VCF 9.1.2 or upgrade vCenter to 9.1.1 first. Broadcom's page names KB 88287 for async patching of VCF 5.x.

Step: check guest alias exposure for VMware Tools (CVE-2026-123894)

For a single Windows VM, Broadcom's FAQ says to run VGAuthCLI.exe list as administrator inside the guest. For many VMs, it points to a PowerCLI example using GuestAliasManager, which needs VMware Tools running, valid guest admin credentials and the "Guest operation alias query" privilege. The FAQ says disabling guest operations and uninstalling or stopping Tools are not workarounds.

How to protect yourself

Google's hardening list, in its own words condensed:

  • Default-deny inbound and egress traffic for vCenter. Egress filtering can block SCP exfiltration and the Slack-based command channel used by LAZYBONES.
  • Enforce firewall rules at the kernel level, because Google says anyone with VAMI access can disable the VAMI firewall. Test with formal change control before using iptables in production.
  • Use Mandiant's VCSA Hardening and Logging tool (github.com/mandiant/vcsa-hardening-tool), STIG benchmarks, privileged access workstations and management-plane isolation.
  • Broadcom's FAQ points to the vSphere Security Configuration and Hardening Guides and the Ports and Protocols tool.

If you run BeyondTrust Remote Support, Google says its earlier post covers CVE-2026-102764, patched in BT26-05; apply that fix as well. Read the vendor's own advisory for details.

What we checked

  • Opened the BleepingComputer article on 2026-11-20 and used it as the pointer; it states that Broadcom has not confirmed exploitation.
  • Opened Broadcom's VMSA-2026-0009 FAQ page on 2026-11-20. It lists five CVEs, the affected products, the fixed versions quoted above, and no workarounds. We did not open the advisory itself, so fixed versions for vCenter 7.x and 9.x are not given here.
  • Opened Google's "ARMORY CASTLE Exploits vSphere" report on 2026-11-20 and copied the indicators exactly with its defanging. Cross-checked: both Google and BleepingComputer give CVE-2026-123890, 19 November 2026 and early September 2026 for the start of exploitation.
  • Cross-checked the product scope between the Broadcom FAQ (vCenter, including 7.0, is affected) and Google (vCenter 7.x and 8.x).
  • The Broadcom FAQ does not mention exploitation; the exploitation claim comes only from Google.
  • Not tested on a live vCenter; no commands were run. Per-CVE CVSS scores are in the advisory and are not given here.

Last tested: 2026-11-20

Sources

Questions people ask

Is CVE-2026-123890 being exploited?

Google Threat Intelligence Group and Mandiant said in a report published on 19 November 2026 that an actor they track as ARMORY CASTLE exploited it as a zero-day from early September 2026. The Broadcom FAQ page we opened does not mention exploitation, and BleepingComputer reported that Broadcom has not confirmed it. Treat the exploitation report as a claim from Google, and patch either way.

Is there a workaround if I cannot patch today?

Broadcom lists no workarounds for any issue in VMSA-2026-0009, and says Enhanced Linked Mode is not a mitigation. Google recommends restricting which hosts can reach vCenter on TCP 443, 2012, 5480 and 22. That reduces exposure but is not a fix.

Does this affect ESX hosts?

Broadcom's FAQ says ESX, NSX, VCF Operations and VCF Automation are not affected by this advisory. Google's report says ESXi hosts were targeted after vCenter was compromised, so a compromised vCenter can put hosts at risk.

Which vCenter version fixes it?

For vCenter 8.0, Broadcom's FAQ names 8.0 U3m. The FAQ does not state fixed versions for vCenter 7.x or 9.x, so read the VMSA-2026-0009 advisory itself.

VMware vCenterBroadcomCVE-2026-123890VMSA-2026-0009Incident response