---
schema: 1
kind: vulnerability
title: "CVE-2026-123890, VMware vCenter Server: an unauthenticated authentication bypass in the Directory Service gives an administrator session; GTIG reports the suspected China-nexus actor ARMORY CASTLE exploited it from early September, Broadcom lists no workaround; fixed in 8.0 U3m, 9.0.2.0200 and 9.1.1.0200 (CVSS 3.1 9.8)"
headline: "vCenter auth bypass exploited since September (GTIG), no workaround: update to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200"
summary: >
  Broadcom's advisory VMSA-2026-0009 of 2026-11-19 fixes CVE-2026-123890, an authentication bypass in the VMware Directory Service of vCenter that needs only network access to vCenter (CVSS 3.1 9.8), with no workaround and, in Broadcom's words, an emergency change. Google Threat Intelligence Group and Mandiant say ARMORY CASTLE, a suspected PRC-nexus actor, exploited it from early September 2026 to move from a compromised remote-support appliance to vCenter, forge administrator SAML sessions and extract domain-controller data from guest virtual disks on ESXi; Broadcom's advisory does not state exploitation. Fixed builds are 8.0 U3m, 9.0.2.0200, 9.1.1.0200 and VMware Cloud Foundation 5.2.5, and vCenter 7.0 has no public fix.
discovered_at: "2026-11-20T05:02:00Z"
updated_at: null
event_date: "2026-11-19"
run_id: 2026-11-20T0356Z-intel
priority: high
immediate_action: null
tags: [vulnerabilities, zero-day, actively-exploited, auth-bypass, pre-auth, nation-state, espionage, china-nexus, patch-available]
regions: [global]
sectors: [public-sector, technology]
entities: ["actor:verdantbamboo", "product:vmware-vcenter-server", "product:vmware-cloud-foundation", "product:vmware-esxi", "product:vmware-sddc-manager", "product:vmware-tools", "malware:bonesaw", "malware:sawsnake", "malware:bearbones", "malware:lazybones"]
techniques: [T1210, T1606.002, T1136.001, T1552.001, T1021.004, T1098.004, T1505.003, T1548.001, T1003.003, T1102.002, T1046]
affected_products: ["VMware vCenter Server", "VMware Cloud Foundation", "VMware SDDC Manager", "VMware Tools"]
cves:
  - id: CVE-2026-123890
    cvss: "9.8"
    epss: null
    type: auth-bypass
    vector: zero-click
    auth: pre-auth
    status: [exploited, patch-available]
    affected: "vCenter 7.0; 8.0 before 8.0 U3m; 9.0 before 9.0.2.0200; 9.1 before 9.1.1.0200; VMware Cloud Foundation 5.x before 5.2.5; Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2 and Telco Cloud Infrastructure 3.0 (KB463116)"
    fixed: "8.0 U3m; 9.0.2.0200; 9.1.1.0200; VMware Cloud Foundation 5.2.5 (async patch KB88287); vCenter 7.0 has no public fix (extended-support customers contact Broadcom Support)"
  - id: CVE-2026-123891
    cvss: "8.1"
    epss: null
    type: sqli
    vector: zero-click
    auth: post-auth
    status: [patch-available]
    affected: "SDDC Manager in VMware Cloud Foundation 9.1, 9.0 and 5.x before the fixed builds"
    fixed: "9.1.1.0200; 9.0.2.0100; 5.2.5"
  - id: CVE-2026-123892
    cvss: "7.2"
    epss: null
    type: rce
    vector: zero-click
    auth: admin-required
    status: [patch-available]
    affected: "SDDC Manager in VMware Cloud Foundation 9.1, 9.0 and 5.x before the fixed builds"
    fixed: "9.1.1.0200; 9.0.2.0100; 5.2.5"
  - id: CVE-2026-123893
    cvss: "6.7"
    epss: null
    type: lpe
    vector: local
    auth: admin-required
    status: [patch-available]
    affected: "SDDC Manager and VCF Installer in VMware Cloud Foundation 9.1, 9.0 and 5.x before the fixed builds"
    fixed: "9.1.1.0200; 9.0.2.0100; 5.2.5"
  - id: CVE-2026-123894
    cvss: "6.7"
    epss: null
    type: priv-esc
    vector: local
    auth: admin-required
    status: [patch-available]
    affected: "VMware Tools for Windows 13.x and 12.3 to 12.5 before the fixed builds (the Q&A names 12.x and 11.x)"
    fixed: "13.1.5.0; 12.5.5 (12.4.10 for 32-bit Windows)"
sources:
  - url: "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495"
    publisher: "Broadcom (VMSA-2026-0009)"
    date: "2026-11-19"
    role: primary
  - url: "https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md"
    publisher: "Broadcom (VMSA-2026-0009 Q&A)"
    date: "2026-11-19"
    role: primary
  - url: "https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/"
    publisher: "Google Threat Intelligence Group / Mandiant"
    date: "2026-11-19"
    role: corroborating
  - url: "https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/"
    publisher: "BleepingComputer"
    date: "2026-11-19"
    role: corroborating
closed_sources: []
evidence:
  - quote: "ARMORY CASTLE exploited this vulnerability in early September 2026 using BONESAW, according to forensic evidence."
    publisher: "Google Threat Intelligence Group / Mandiant"
    source_url: "https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/"
  - quote: "A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system."
    publisher: "Broadcom (VMSA-2026-0009)"
    source_url: "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495"
  - quote: "The vCenter issue qualifies under ITIL methodologies as an emergency change, requiring prompt action from your organization."
    publisher: "Broadcom (VMSA-2026-0009 Q&A)"
    source_url: "https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md"
  - quote: "While Broadcom has not confirmed that the flaw was exploited, researchers at Google's Mandiant have documented attacks exploiting CVE-2026-123890."
    publisher: "BleepingComputer"
    source_url: "https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/"
verification: multi-source
sourcing_note: >
  Broadcom is the disclosing vendor for its own product and credits Mandiant; its advisory and Q&A do not state exploitation. The exploitation claim, its date and the intrusion chain rest on Google Threat Intelligence Group and Mandiant alone, and BleepingComputer relays them while noting that Broadcom has not confirmed exploitation. GTIG describes one intrusion and names no victim sector or country. Attribution to ARMORY CASTLE is GTIG's, made on tooling and technique overlap.
confidence: high
references: ["2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day", "2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape"]
deep_dive: false
deep_dive_category: null
org_triage: null
classification:
  reliability: A
  credibility: 2
watchlist_hit: false
actions:
  - "Update every vCenter Server to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m (VMware Cloud Foundation 5.x to 5.2.5 through KB88287) now as an emergency change, and until it is in, drop inbound TCP 2012 to vCenter from every address that is not an allowlisted management host, as Google's hardening guidance lists, after testing because TCP 2012 is the vCenter SSO control-interface RPC, because GTIG reports exploitation since early September and Broadcom lists no workaround."
  - "On every vCenter that was reachable from an internal host before the update, list the SSO and local administrators on vsphere.local that nobody created, review the SSO signing material and ESXi authorized_keys files, because the actor extracted the SAML signing key and created accounts, which updating does not undo."
updates: []
migrated_from: null
---

Broadcom's advisory VMSA-2026-0009 of 2026-11-19 fixes CVE-2026-123890, an authentication bypass in the VMware Directory Service of vCenter: an actor with network access can bypass authentication and gain unauthorized access without credentials (CVSS 3.1 9.8) ([Broadcom, 2026-11-19](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)). Broadcom lists no workaround, calls the issue an emergency change and does not state exploitation ([Broadcom, 2026-11-19](https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md)). Broadcom credits Mandiant with the report ([Broadcom, 2026-11-19](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)), and Google Threat Intelligence Group and Mandiant say ARMORY CASTLE, a suspected PRC-nexus actor, exploited it in early September 2026 with its BONESAW utility, according to forensic evidence ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)). GTIG describes one intrusion that reached an internal vCenter from a Remote Support appliance compromised through the earlier BeyondTrust zero-day and names no victim sector or country ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)); BleepingComputer notes that Broadcom has not confirmed the exploitation ([BleepingComputer, 2026-11-19](https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/)).

The flaw is a session-key disclosure over DCE/RPC in the rpc_srp_verifier service on TCP 2012 that yields an authenticated administrator@vsphere.local session; BONESAW then read the Directory Service database, extracted the SAML signing key and created an SSO administrator, SAWSNAKE forged administrator SAML assertions, and the actor switched SSH on through the appliance management API, took the master symmetric key and the PostgreSQL credential file, switched SSH off again, logged in to ESXi hosts, planted an authorized_keys entry and extracted the domain database, registry hives and DNS data from Windows guest virtual disks before copying an archive out over SCP ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)).

Broadcom's response matrix names the fixes: vCenter 9.1 in 9.1.1.0200, 9.0 in 9.0.2.0200, 8.0 in 8.0 U3m, VMware Cloud Foundation 5.x in 5.2.5 through KB88287 and Telco Cloud through KB463116; vCenter 7.0 has no public fix, and extended-support customers contact Broadcom Support ([Broadcom, 2026-11-19](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)). The 8.0 U3m and 9.0.2.0200 updates block later upgrades to VCF 9.1.1 until 9.1.2 ([Broadcom, 2026-11-19](https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md)).

**Exposure:** vCenter 7.0, 8.0, 9.0 and 9.1 before the fixed builds; the only stated prerequisite is network access to vCenter, and GTIG's actor reached it from an internal Linux appliance, so exposure does not require an internet-facing vCenter ([Broadcom, 2026-11-19](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495); [GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)). The running build is in the vSphere Client Summary tab or in PowerCLI ([Broadcom, 2026-11-19](https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md)).

**Detection:** in the vCenter appliance management audit log, SSH switched on and then off again, a new local or SSO administrator, and reads of the Directory Service database, the master key and the PostgreSQL credential file; in network telemetry, sweeps of ports 2012, 5480 and 9080 from a Linux appliance that is not a management host; on ESXi, logins as vpxuser or root, a new authorized_keys entry and a hidden directory on a VMFS volume ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)). GTIG advises hardening the vCenter appliance beyond patching, and because BONESAW extracts the SAML signing key and the actor created accounts, the compromise check covers SSO and local administrators, signing material and ESXi keys from early September on ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)).

**Triage:** SSH enablement through the management API alone does not identify this activity; in GTIG's case it followed internal port sweeps from a non-management appliance and was reversed after the credential reads ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/)).

**Defender takeaway:** treat the update as an emergency change and plan around vCenter 7.0, which has no public fix; until it is in, GTIG's hardening guidance lists dropping inbound TCP 2012 from non-allowlisted addresses, to be tested first because the port carries SSO traffic ([GTIG, 2026-11-19](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere/); [Broadcom, 2026-11-19](https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md)).
