🎧 Listen to this article: हिंदी · English · தமிழ் · తెలుగు
🌍 Read this in your language: हिंदी · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · ଓଡ଼ିଆ · 日本語 · 中文
When attackers breach an application, typical incident response focuses on patching software, terminating sessions, and rotating keys. The equation changes completely when adversaries bypass the guest operating system and pull raw virtual disks directly from underlying hypervisors.
As of November 21, 2026, enterprise IT operations and security teams face that reality. Broadcom has published an emergency advisory for a critical zero-day flaw in VMware vCenter Server that suspected state-sponsored cyber espionage operators exploited in targeted intrusions for more than two months. Tracked as CVE-2026-123890 with a CVSS rating of 9.8, the bug enables remote attackers with network access to bypass authentication and gain full administrative privileges over vCenter. Investigations by Google Threat Intelligence Group and Mandiant revealed that attackers used this foothold to pivot directly to ESXi hosts, pulling complete Active Directory database files straight off virtual storage.
How the Remote Support Breach Reached VMware
The campaign has been attributed to Armory Castle, an espionage threat actor formerly tracked as UNC5221. Rather than finding an exposed vCenter server on the public internet, the group chained two separate zero-day vulnerabilities across perimeter and core infrastructure.
The intrusion began with CVE-2026-102764 in BeyondTrust Remote Support appliances, where an internal messaging flaw allowed remote actors to execute file operations. While BeyondTrust patched SaaS tenants by October 9, 2026, self-hosted appliances that missed updates remained exposed.
From that gateway, Armory Castle moved onto internal Linux appliances lacking EDR agents, deploying web shells like SLIMSAVAGE (ActiveSer.jsp) and backdoors like LAZYBONES (/usr/bin/vmtoolscs).
From these staging points, the attackers reached internal vCenter servers by September 2026. This confirms that keeping management interfaces private provides little defense when edge appliances lack internal segmentation.
What the vCenter Flaw Gave the Attackers
The vulnerability affects VMware Directory Service (vmdir), the directory service component governing vCenter Single Sign-On (SSO). An attacker with network line-of-sight to vmdir can bypass authentication entirely without valid credentials.
Mandiant observed attackers establishing sessions as [email protected], the top administrative tier in vSphere. Broadcom confirmed that the flaw affects deployments whether Enhanced Linked Mode is enabled or disabled.
Once inside, Armory Castle used custom utilities to entrench their access:
- BONESAW: A custom Golang utility that created rogue Single Sign-On administrator accounts and copied the vCenter directory database in Lightning Memory-Mapped Database (LMDB) format.
- Certificate Theft: The stolen database contained credentials and cryptographic signing certificates used to validate VMware authentication tokens.
- SAWSNAKE: A utility built to forge Security Assertion Markup Language (SAML) tokens using the stolen signing keys. Services accepting these forged tokens grant administrative access without prompting for passwords or multi-factor authentication (MFA).
Installing Broadcom's update fixes the authentication bypass. However, it does not remove administrator accounts created during the intrusion or revoke stolen signing certificates. Responders must audit both.
The Hypervisor Threat to Active Directory
The most serious activity occurred beneath the virtual machines. After compromising vCenter, Armory Castle moved into the underlying ESXi hypervisors.
In typical intrusions, attackers query Windows Domain Controllers through administrative protocols, generating event logs like Event ID 4624 (logon) and Event ID 4672 (special privileges) that alert EDR agents.
Armory Castle bypassed Windows defenses completely. Operating from the ESXi host console, the group directly accessed virtual machine disk files (.vmdk) belonging to virtualized Domain Controllers.
From these disks, the attackers extracted:
- The Active Directory database (
NTDS.dit), containing all domain password hashes and Kerberos keys. - The Windows
SYSTEMandSECURITYregistry hives, containing the boot keys needed to decrypt password hashes.
The group staged the extracted files in a temporary datastore folder, compressed them, exfiltrated the archive through obfuscation infrastructure (including 103.147.251[.]5 and 176.9.89[.]66), and deleted the staging directory. Because theft occurred at the hypervisor storage layer, Windows guest monitoring saw nothing.
Affected Versions and the Cloud Foundation Upgrade Trap
Broadcom released advisory VMSA-2026-0009 on November 19, 2026, and revised it on November 20 to clarify guidance for vSphere 7.
The fixed builds for vCenter Server are:
- vCenter 9.1.x — update to 9.1.1.0200
- vCenter 9.0.x — update to 9.0.2.0200
- vCenter 8.0 — update to 8.0 Update 3m
- vCenter 7.0 — general support ended on October 2, 2025; contact Broadcom under an active extended support contract.
Advisory VMSA-2026-0009 also addresses four additional flaws:
- CVE-2026-123891: SQL injection in SDDC Manager (fixed in 9.1.1.0200, 9.0.2.0100, and 5.2.5).
- CVE-2026-123892: Authenticated command injection in SDDC Manager.
- CVE-2026-123893: Local privilege escalation in SDDC Manager.
- CVE-2026-123894: Token validation flaw in VMware Tools for Windows, permitting local privilege escalation via guest alias mapping (fixed in 13.1.5.0, 12.5.5, and 12.4.10).
The Cloud Foundation Upgrade Sequencing Trap
For organizations running VMware Cloud Foundation (VCF), applying standalone vCenter patches can break future upgrades. Applying vCenter 8.0 Update 3m or 9.0.2.0200 blocks a subsequent upgrade to VCF 9.1.1 because the patched build is newer than the standard VCF 9.1.1 release target.
Organizations planning a VCF 9.1 upgrade must upgrade vCenter to 9.1.1 first, and then apply the 9.1.1.0200 security patch directly to that branch.
Step-by-Step Response and Remediation Procedure
Remediating this intrusion requires a coordinated response across virtualization and identity teams.
Step 1: Isolate Management Interfaces
Place vCenter management interfaces behind firewall rules immediately. Block unauthorized access to ports 443, 389, and 636:
# Verify restricted access to vCenter ports from administrative subnets only
grep -E ":(443|389|636)" /var/log/firewall/traffic.log | grep -v "192.168.10.0/24"
Step 2: Apply VMSA-2026-0009 Patches
Update vCenter using the VMware Appliance Management Interface (VAMI) or the appliance shell:
# Check current build and install updates via appliance shell
vpxd -v
software-packages stage --url
software-packages install --processRebootRequirement
Step 3: Audit Single Sign-On Accounts
Inspect the local identity store for unauthorized accounts created since September 2026:
# Enumerate all accounts in the vsphere.local domain
/usr/lib/vmware-vmdir/bin/vdcli -u administrator -w 'REPLACE_WITH_ADMIN_PASSWORD' -m users -a list
Review group memberships, paying special attention to the Administrators group in the vSphere Client.
Step 4: Rotate STS Signing Certificates
Because attackers may hold stolen SAML signing keys, regenerate the Security Token Service (STS) certificates to invalidate forged tokens:
# Launch the VMware Certificate Manager to regenerate STS certificates
/usr/lib/vmware-vmca/bin/certificate-manager
Choose the option to replace the machine SSL certificate and VMCA root certificates.
Step 5: Audit ESXi Host and Storage Logs
Search ESXi hosts for unauthorized shell access and suspicious files:
# Search for known malware filenames across storage mounts
find / -name "vmtoolscs" -o -name "ActiveSer.jsp" 2>/dev/null
# Review recent ESXi shell history for virtual disk interaction
cat /var/log/shell.log | grep -i "vmdk"
Inspect datastores hosting Domain Controllers for unexpected folder archives or copied .vmdk files.
Step 6: Reset Active Directory Enterprise Credentials
If evidence indicates hypervisor access to Domain Controller storage, treat the Windows domain as compromised:
- Reset the Active Directory Kerberos Ticket Granting Service account (
krbtgt) password twice, waiting 24 hours between resets. - Force password resets for all Domain Admin and privileged service accounts.
- Invalidate all active Kerberos tickets across the domain.
Conclusion
The VMware vCenter zero-day vulnerability CVE-2026-123890 demonstrates how advanced threat actors chain edge device exploits to reach core virtualization platforms. By pivoting to ESXi hypervisors and extracting Active Directory databases directly from storage, attackers bypass traditional operating system logging. Patching the software is a vital first step, but complete recovery requires auditing single sign-on accounts, regenerating signing certificates, and resetting domain identities.
Merits
- Closes a critical 9.8 CVSS authentication bypass in VMware Directory Service.
- Rotating STS signing certificates invalidates forged tokens generated by tools like SAWSNAKE.
- Restricting vCenter management ports stops lateral movement from compromised perimeter devices.
- Hypervisor audits reveal data theft that guest operating system tools cannot detect.
Demerits
- Applying patches and restarting services requires planned maintenance downtime.
- The Cloud Foundation 9.1 sequencing dependency complicates standard patching workflows.
- Performing a double
krbtgtpassword reset requires careful timing to prevent authentication disruption.
Caution
This article is for educational and defensive purposes only. Replace all placeholder values such as REPLACE_WITH_ADMIN_PASSWORD and 192.168.10.0/24 with your organization's verified configurations. Readers must review official Broadcom documentation and test updates in non-production environments before applying them.
Frequently asked questions
- What is CVE-2026-123890? — It is a critical authentication bypass vulnerability in VMware vCenter Server's Directory Service with a CVSS score of 9.8.
- Who exploited this vulnerability? — An espionage group tracked as Armory Castle (formerly UNC5221), suspected of links to China, exploited the flaw in targeted intrusions.
- How did attackers reach vCenter if it was not public? — They breached an internal network via a BeyondTrust Remote Support zero-day and pivoted through unmonitored Linux appliances.
- Why are Active Directory credentials at risk? — Attackers pivoted from vCenter to ESXi hosts, copying raw virtual disk files containing
NTDS.ditdirectly from hypervisor storage. - Does Enhanced Linked Mode affect vulnerability status? — Broadcom confirmed the flaw impacts vCenter deployments whether Enhanced Linked Mode is enabled or disabled.
- What is the VCF 9.1 upgrade issue? — Applying vCenter 8.0 Update 3m or 9.0.2.0200 creates a build newer than VCF 9.1.1, blocking subsequent upgrades unless vCenter is updated to 9.1.1 first.
- Is applying the patch enough to eliminate the threat? — No, organizations must also audit single sign-on accounts, regenerate STS signing certificates, and reset domain passwords if hypervisor theft occurred.
Tags
#vmware #vcenter #cve2026123890 #cybersecurity #armorycastle #activedirectory #infosec #sysadmin #virtualization
Prompt-Injection Defense Checklist
The controls that actually reduce the blast radius when your app feeds untrusted text to an LLM. Enter your email — you'll get the PDF instantly, plus new posts on AI, security & Linux.
Free. No spam — unsubscribe in one click.


Responses
Sign in to leave a response.