VMware vCenter Zero-Day Demands Patching and Forensic Checks

Avatar photo

ByRyan Mitchell

November 22, 2026

Google threat analysts detail how Armory Castle used a vCenter zero-day to reach ESXi hosts and extract virtual-machine data, while CISA orders urgent remediation.

The clearest urgent cybersecurity warning in the latest reporting concerns VMware vCenter Server. Google Threat Intelligence Group (GTIG) and Mandiant describe an intrusion in which attackers used a zero-day flaw to move from vCenter into ESXi hosts and extract files from virtual machines. CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20, classifying exploitation as active. Federal civilian agencies must remediate by November 23 and conduct forensic triage.

The intrusion set is identified as Armory Castle. GTIG and Mandiant say the campaign used two zero-days and involved five newly observed malware families and utilities: SLIMSAVAGE, CAGEMATCH, BONESAW, SAWSNAKE and BEARBONES. Researchers had previously observed another tool, LAZYBONES. CISA’s assessment describes the flaw’s exploitation as active and automatable, with total technical impact. That is a reason to treat the issue as an immediate response priority, not routine maintenance.

The compromise went beyond gaining access to vCenter. According to GTIG and Mandiant, attackers enabled SSH through the vCenter Server Appliance Management Interface, extracted the vCenter master key and PostgreSQL credentials, and accessed ESXi systems as root and vpxuser. They added an SSH key to an ESXi root account and extracted guest virtual-machine files, including Windows NTDS and registry data. The stolen files could provide sensitive information about an organization’s directory environment and systems.

That sequence matters because installing an update does not establish that an affected system is clean. A stolen credential or added SSH key may remain useful after the original vulnerability is closed. Since vCenter manages virtual infrastructure, a compromise there can put connected hosts and workloads at risk. Organizations should assess the appliance and the systems it controls, not treat vCenter as an isolated server.

Broadcom has published fixes for affected vCenter versions, but administrators should consult the vendor’s current advisory to identify the update for their specific product branch. The supplied reporting does not verify a published fix for vCenter 7.0, so operators on that release should seek direct guidance from Broadcom rather than assume another version’s update applies. Federal civilian agencies face CISA’s November 23 deadline; other organizations should also prioritize action because exploitation is active.

Small IT teams can start by listing every vCenter appliance and associated ESXi host, including deployments outside the main production environment. Confirm each version, apply the relevant Broadcom update and verify that installation completed. Preserve logs before changes that could erase evidence. Review for unexpected SSH enablement through VAMI, unfamiliar administrator accounts, new or altered SSH keys, unusual root or vpxuser access, and guest-file access that does not match normal administration.

If checks reveal unexplained changes, patching alone may leave an attacker’s access intact. Restrict access while the incident is assessed, review connected identity systems and virtual machines, and bring in incident-response help if the team cannot determine what was accessed. CISA’s direction to conduct forensic triage is a reminder that remediation includes finding out whether exploitation occurred—not only closing the vulnerable entry point.

The supplied material also describes active exploitation of an Apache Roller issue, but does not provide sufficiently verified details here for a dependable patch instruction. The vCenter compromise and CISA’s deadline are the clearest actionable developments in the reporting. For operators, the immediate job is twofold: update the vulnerable system and investigate whether attackers used it to establish access elsewhere.

Leave a Reply

Your email address will not be published. Required fields are marked *