CVE-2026-123890: VMware vCenter Zero-Day Exploit Analysis

A critical zero-day in VMware Directory Service allowed attackers to forge SAML tokens and gain full SSO admin privileges across vCenter instances.

TL;DR

  • CVE-2026-123890 is a critical (CVSS 9.8) vulnerability in the VMware Directory Service (vmdir) exploited as a zero-day for over two months prior to Broadcom patches released on 19 November 2026.
  • Threat group Armory Castle (UNC5221 / Warp Panda) established initial access via a BeyondTrust Remote Support zero-day (CVE-2026-102764), traversed internal Linux appliances, and targeted vCenter servers in early September 2026.
  • Attackers deployed a custom tool named Bonesaw to exploit vmdir, exfiltrate the Lightning Memory-Mapped Database (LMDB), extract SAML signing keys, and create rogue Single Sign-On (SSO) administrator accounts across vCenter 7.x and 8.x deployments.
  • Post-exploitation activities included secondary tool usage for SAML token forgery, theft of the vCenter master encryption key and database credentials, and lateral movement directly onto underlying ESXi hypervisors.
  • Broadcom has patched the flaw in vCenter versions 8.0 U3m, 9.0.2.0200, and 9.1.1.0200. Legacy vCenter 7.0 reached End of General Support in October 2025 and lacks an official public patch.

Broadcom has issued security updates to fix cve-2026-123890 vmware vcenter, a critical authentication bypass and database extraction vulnerability residing in the VMware Directory Service (vmdir). Carrying a CVSS v3/v4 severity rating of 9.8, the flaw allows unauthenticated, remote attackers with network access to vmdir to obtain administrative privileges on target vCenter Server instances. Mandiant discovered the activity and reported the flaw to Broadcom after identifying active in-the-wild exploitation spanning more than two months prior to the public advisory on 19 November 2026.

The campaign has been attributed by Mandiant to Armory Castle, a sophisticated threat group previously tracked as UNC5221 and Warp Panda. Evidence indicates that Armory Castle possessed working exploit material for CVE-2026-123890 prior to 29 July 2026—predating the public disclosure of CVE-2026-59309, a separate vCenter authentication bypass. In this campaign, initial access was gained through CVE-2026-102764, a zero-day in BeyondTrust Remote Support. The attackers subsequently pivoted through internal Linux appliances before reaching administrative vCenter interfaces in early September 2026.

Once network access to vCenter was secured, the threat actor utilized a specialized exploit tool designated Bonesaw to extract raw directory databases, steal SAML signing certificates, forge administrative identity tokens, and compromise the underlying ESXi hypervisor layer. According to reporting by SecurityWeek, the vulnerability presents systemic risk to hypervisor control planes, requiring infrastructure teams to apply vendor patches, audit directory logs, and execute full credential and signing key rotations across compromised environments.

Threat Overview: The CVE-2026-123890 Zero-Day Campaign

CVE-2026-123890 represents a maximum-severity flaw in the VMware Directory Service (vmdir), the central identity store for vSphere Single Sign-On (SSO). Rated 9.8 on the CVSS scale, the vulnerability permits remote, unauthenticated actors to bypass authentication boundaries and achieve complete control plane takeover. The operational window of this threat was substantial: Armory Castle maintained unmonitored access to target virtualized infrastructure for over eight weeks before patches were finalized and published on 19 November 2026.

Mandiant’s incident response investigations revealed that Armory Castle targeted high-value enterprise environments globally. The threat actor demonstrated advanced operational security, maintaining zero-day capabilities across multiple enterprise platforms simultaneously. Broadcom’s safety fixes were introduced across active release lines, specifically vCenter Server versions 8.0 U3m, 9.0.2.0200, and 9.1.1.0200. However, environments running legacy vCenter 7.x deployments face severe exposure. vCenter 7.0 reached End of General Support (EOGS) in October 2025 and does not have an official public patch, despite being explicitly targeted by the Bonesaw exploit tool.

Unsupported Software Risk

The Bonesaw exploit tool functions against both vCenter 7.x and 8.x releases. Because vCenter 7.0 passed End of General Support in October 2025, organisations running 7.x deployments must migrate immediately or implement strict network segmentation to block remote access to vmdir network interfaces.

Anatomy of the Kill Chain: Perimeter Breach to Linux Pivoting

The deployment of the Bonesaw tool was not an isolated perimeter event; it was the middle phase of an intrusion chain designed to traverse enterprise trust boundaries. Armory Castle established initial entry into target environments by exploiting CVE-2026-102764, an unpatched zero-day flaw in BeyondTrust Remote Support appliances. By breaching edge remote access infrastructure, the attackers bypassed traditional external perimeter firewalls and gained an initial foot-hold inside internal management zones.

From the compromised BeyondTrust appliances, the threat actors engaged in internal reconnaissance and lateral movement. Rather than attempting direct, noisy connections from edge systems to critical core infrastructure, Armory Castle routed traffic through secondary internal Linux appliances. This staging phase allowed the group to blend malicious administrative traffic with legitimate lateral appliance communication across enterprise subnets.

By early September 2026, Armory Castle had established stable proxy paths to target internal vCenter administrative instances. The success of this pivot highlights standard architectural control failures in enterprise environments:

  • Flat Management Routing: Absence of strict stateful firewall inspection between perimeter remote support appliances and internal hypervisor management networks.
  • Over-Privileged Appliance Subnets: Linux security appliances and management tools allowed unrestricted TCP routing to vCenter identity services.
  • Inadequate Interface Microsegmentation: Exposure of the vmdir service ports (TCP 389/636) beyond the specific local nodes or localized administrative jump boxes required for directory operations.

Lateral Movement Trajectory

Perimeter Boundary (BeyondTrust Remote Support zero-day CVE-2026-102764) → Internal Pivoting (Compromised Linux Appliances) → Management Subnet Routing → Hypervisor Control Plane (vCenter vmdir via CVE-2026-123890).

Inside VMware Directory Service and the Bonesaw Exploit Tool

To understand how Armory Castle compromised vSphere SSO, infrastructure engineers must examine the role of the VMware Directory Service (vmdir). In a vSphere architecture, vmdir operates as an LDAP-compliant directory server. It manages multi-tenant identity domain state, security domains (such as vsphere.local), service principal names, solution user identities, and public key infrastructure (PKI) associations across vCenter services.

The underlying storage mechanism for vmdir is the Lightning Memory-Mapped Database (LMDB), an embedded key-value store known for high read performance. LMDB stores directory objects directly on the vCenter filesystem within memory-mapped binary files (typically located at /storage/db/vmware-vmdir/data.mdb). Under normal operating conditions, access to LMDB data is strictly mediated by the vmdird daemon process via authenticated LDAP queries.

CVE-2026-123890 exposes a severe weakness within the processing logic of vmdird. Broadcom and Mandiant have not publicly disclosed the exact internal memory corruption or authentication logic flaw mechanism inside vmdir that allows database extraction. However, threat analysis confirms that Armory Castle’s custom tool, Bonesaw, leveraged this zero-day state to bypass authentication controls on TCP ports 389/636 and extract the complete LMDB database file from vulnerable vCenter 7.x and 8.x instances.

# Conceptual layout of vmdir directory storage on vCenter Appliance
/storage/db/vmware-vmdir/
├── data.mdb    # Raw Lightning Memory-Mapped Database (LMDB) containing identities & keys
└── lock.mdb    # LMDB lock state file

The sophistication of Armory Castle is underscored by intelligence confirming that the group held working knowledge of CVE-2026-123890 prior to 29 July 2026. This date is significant: it marks the public disclosure of CVE-2026-59309, a separate vCenter authentication bypass bug. Forensic evidence collected by Mandiant demonstrated that Bonesaw was actively executed against target vCenter servers that had already been fully patched against CVE-2026-59309, confirming that Armory Castle maintained distinct, parallel zero-day capabilities tailored specifically for vCenter directory services.

SAML Signing Material Theft and Persistence Techniques

Exfiltration of the raw LMDB file grants an attacker full insight into the internal identity domain. Because the database contains serialized domain objects, Armory Castle extracted the vSphere Security Token Service (STS) SAML signing certificates and associated private keys. In a vSphere deployment, the SAML signing key is the apex secret: it authenticates token assertions issued across all registered vSphere components.

With the SAML signing material stolen, Armory Castle achieved complete privilege escalation and administrative persistence through several distinct techniques:

  1. Rogue SSO Admin Account Creation: Attackers modified or injected directory records within vmdir to establish a new, unauthorized Single Sign-On administrator account directly inside the vsphere.local domain.
  2. Custom SAML Token Forgery: Using a secondary custom tool (the technical name and internal signature of this second tool have not been disclosed), the attackers generated forged SAML assertions offline. Signed with the stolen private key, these “Golden SAML” tokens allowed the threat group to present valid, high-privilege assertions directly to vCenter web services, bypassing standard interactive login routines and multi-factor authentication (MFA) controls.
  3. Master Encryption Key Extraction: Armory Castle accessed the vCenter master encryption key (stored in configuration files such as /etc/vmware-vpx/vpxd.cfg) and exfiltrated the underlying vpxd relational database credentials.
  4. Persistence Backdoors: By pairing forged identity tokens with administrative permissions, the group established persistent web shells and backdoors inside vCenter appliance services, ensuring long-term access independent of standard user password changes.
# Diagnostic check: Querying VMware Endpoint Certificate Store (VECS) for STS Signing Certificates
/usr/lib/vmware-vmafd/bin/vecs-cli entry list --store TRUSTED_ROOTS --text

# Output displays trusted signing certificates used for SAML validation
# If private keys are compromised, applying patches alone WILL NOT revoke forged SAML tokens

Pivoting to the Hypervisor: From vCenter Control Plane to ESXi Host

In VMware vSphere environments, vCenter acts as the centralized management controller, interacting with individual ESXi hypervisor hosts via the VMware Virtual Center Agent daemon (vpxa) and host daemon (hostd). When Armory Castle compromised vCenter database secrets and master encryption keys, the security boundary separating the management server from underlying physical hypervisors collapsed.

The exfiltration of the vpxd database provided the threat actor with stored authentication credentials, host connection tokens, and SSH identity keys used by vCenter to manage ESXi nodes. With these credentials decrypted using the stolen master encryption key, Armory Castle pivoted laterally from the vCenter server control plane directly to underlying ESXi host shells and administrative interfaces.

Achieving root or near-root privileges at the ESXi hypervisor level gives attackers total control over virtual workloads and storage infrastructure:

  • Virtual Machine Disk (VMDK) Exfiltration: Direct mounting and copying of offline or active .vmdk files straight from VMFS datastores, bypassing guest OS logging and access controls.
  • Hypervisor Memory Extraction: RAM inspection of active virtual machines to harvest unencrypted credentials, runtime secrets, and session state.
  • Persistent Host Implants: Modification of ESXi system binaries, VIB (VMware Installation Bundle) packages, or startup scripts to maintain access across hypervisor reboots.
  • Datastore Reconnaissance: Enumeration of enterprise storage volumes, snapshot backups, and domain controller image files stored across cluster storage pools.

Blast Radius Assessment

Compromise of the vCenter management layer invalidates the security assumptions of all hosted guests. Once an attacker obtains master encryption keys and ESXi host credentials, guest-level security controls (such as endpoint detection and response agents inside virtual machines) can be fully bypassed at the hypervisor storage level.

Detecting Armory Castle Activity and SAML Golden Ticket Forgery

Because Armory Castle relied on low-level directory database exfiltration and valid cryptographic tokens, traditional signature-based detection mechanisms often miss this activity. Incident responders and SOC teams must implement log auditing focused on vmdir interaction, identity modifications, and unusual certificate usage.

1. Auditing VMware Directory Service (vmdir) Anomalies

Inspect /var/log/vmware/vmdir/vmdird-syslog.log on vCenter appliances for unexpected connection origins, high-volume data read operations, or structural schema modifications. Unauthenticated network requests originating from internal Linux appliances or non-administrative IP subnets targeting TCP ports 389/636 must be flagged immediately.

# Diagnostic check: Search vmdir logs for unauthenticated or abnormal LDAP access patterns
grep -iE "(Failed authentication|bind failed|Unauthenticated|client connection)" /var/log/vmware/vmdir/vmdird-syslog.log

# Inspect file access timestamps and process execution against the raw LMDB data file
ls -lu /storage/db/vmware-vmdir/data.mdb

2. Identifying Rogue SSO Admin Accounts and Certificate Access

Execute identity checks within the vSphere domain using administrative command-line utilities. Verify that all accounts listed in the vsphere.local administrators group match known, authorized personnel.

# Diagnostic check: List all domain users in the vsphere.local directory
/usr/lib/vmware-vmdir/bin/dir-cli user list --login [email protected]

# Diagnostic check: Review group membership for the Administrators group
/usr/lib/vmware-vmdir/bin/dir-cli group listgroups --name Administrators

3. Analyzing SSO Token and Authentication Logs

Forged SAML tokens presented to vCenter web services produce operational anomalies within vSphere SSO logs located at /var/log/vmware/sso/. Compare assertion timestamps, client IP addresses, and User-Agent headers against standard administrative jump box traffic. Look for valid administrator logins originating from internal server subnets, security appliances, or unexpected external jump points.

Remediation and Mitigation Strategy for Enterprise Engineering Teams

Addressing CVE-2026-123890 requires a strict, multi-stage remediation workflow. Applying vendor security patches addresses the remote directory flaw, but it does not invalidate stolen SAML keys, rogue administrator accounts, or compromised host credentials already extracted by threat actors.

vCenter Release Branch Vulnerable Status Fixed Version Target Remediation Action Required
vCenter Server 9.1.x Vulnerable 9.1.1.0200 Apply Broadcom patch update immediately.
vCenter Server 9.0.x Vulnerable 9.0.2.0200 Apply Broadcom patch update immediately.
vCenter Server 8.0.x Vulnerable 8.0 U3m Apply Broadcom patch update immediately.
vCenter Server 7.0.x Vulnerable None (EOGS) No public patch. Isolate network access; upgrade to supported release.

Post-Patch Hardening and Secrets Invalidation Checklist

If an enterprise suspects or confirms zero-day exposure prior to patching, engineering teams must complete a full control plane reset post-patching:

  1. Rotate SAML STS Signing Certificates: Use the VMware lsdoctor tool or standard vSphere Certificate Manager scripts to regenerate the internal STS certificate authority and service signing keys. This step revokes all forged SAML tokens created by Armory Castle’s secondary tooling.
  2. Re-Key Master Encryption Secrets: Execute master key regeneration routines on vCenter to protect stored passwords and database connection parameters.
  3. Reset vCenter Database Credentials: Update internal service account passwords used by vpxd to communicate with underlying relational databases.
  4. Rotate ESXi Host Secrets: Re-establish host trust relationships across all managed hypervisors. Update hypervisor root passwords, rotate SSL management certificates, and reset administrative SSH keys.
  5. Purge Rogue Accounts: Remove any unauthorized SSO administrative accounts identified during directory log audits.
  6. Network Microsegmentation: Implement strict stateful firewall access control lists (ACLs) restricting access to vCenter ports 389/636 (vmdir) and 443 (HTTPS) strictly to trusted management subnets and dedicated jump systems.
# Diagnostic check: Regenerating STS Certificates (Test thoroughly in staging environments)
# Download official VMware lsdoctor tool and run python check script
python lsdoctor.py --stsfix

# Verify STS certificate validity period post-rotation
/usr/lib/vmware-vmafd/bin/vecs-cli entry list --store vSphere-SSO --text

Key Takeaways for Infrastructure and Security Leaders

The exploitation of CVE-2026-123890 by Armory Castle highlights several strategic realities for modern enterprise infrastructure leaders:

  • Hypervisor Management Planes are Primary Targets: Sophisticated threat actors prioritize hypervisor control planes because breaching a single vCenter provides implicit access to thousands of guest workloads, bypassing endpoint detection tools.
  • Patching Does Not Equal Revocation: In vulnerability campaigns involving identity stores, applying a vendor patch closes the entry vector but leaves persistent cryptographic backdoors intact. Key and certificate rotation must be built into incident response playbooks.
  • End-of-Support Technical Debt is an Unacceptable Risk: Running software past its End of General Support date—such as vCenter 7.0—leaves mission-critical infrastructure exposed without vendor security patches when zero-day exploits emerge.
  • Enforce Zero-Trust Management Boundaries: Edge security tools (such as remote access devices) must never possess uninhibited IP routing to management plane subnets. Microsegmentation must isolate vmdir interfaces from internal lateral movement paths.

Frequently asked questions

Which vCenter versions are vulnerable to CVE-2026-123890?

CVE-2026-123890 affects VMware vCenter Server releases across the 7.x, 8.x, and 9.x branches that run the VMware Directory Service (vmdir). Broadcom has released updates for supported branches, specifically vCenter Server 8.0 U3m, 9.0.2.0200, and 9.1.1.0200. Organizations must update vulnerable instances immediately to close the attack vector.

Is there an official Broadcom patch for vCenter 7.x instances?

No official public patch is available for vCenter Server 7.0. The 7.x branch reached End of General Support (EOGS) in October 2025. Because the Bonesaw exploit tool actively targets vCenter 7.x deployments, organisations operating legacy 7.0 servers must enforce strict network isolation and migrate immediately to a supported release line.

How did attackers obtain initial entry prior to exploiting vCenter?

Armory Castle established perimeter entry by exploiting CVE-2026-102764, a zero-day vulnerability in BeyondTrust Remote Support. After breaching the edge remote access system, the attackers pivoted laterally across internal Linux appliances on the corporate network until they obtained IP connectivity to internal vCenter management interfaces.

Why is patching vCenter insufficient if SAML signing keys were compromised?

Patching CVE-2026-123890 stops unauthenticated attackers from making new unauthorized calls to vmdir, but it does not revoke stolen cryptographic assets. If attackers exfiltrated the STS SAML signing certificate, they can generate valid identity tokens offline. Security teams must rotate SAML signing certificates, re-key master encryption stores, and reset host passwords to eliminate persistence.

Sources and further reading

This article was drafted with AI assistance from the publicly cited sources and passed automated checks for structure and sourcing. Verify critical details against the vendor advisories linked above before acting.