Security alert · Critical
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
· 5 minutes read · Centoculus Security Team
Known since · attacks confirmed since
Affected: VMware vCenter Server 8.0, 9.0 and 9.1, including the vCenter in VMware Cloud Foundation (also 5.x), vSphere Foundation and Telco Cloud. vSphere 6.5, 6.7 and 7.0 are presumed affected. ESX is not affected.
What happened
On 19 November 2026 Broadcom published security advisory VMSA-2026-0009. It fixes a critical authentication bypass in the VMware Directory Service of vCenter Server, rated 9.8 on the CVSS scale. An attacker who can reach vCenter over the network can bypass authentication without a login and gain unauthorized access. Broadcom treats the vCenter update as an emergency change. It offers no workaround.
Broadcom has not confirmed any attacks itself. Google's Mandiant reported the flaw, and Mandiant and the Google Threat Intelligence Group published a report on the same day. They say a suspected Chinese state-sponsored group, tracked as Armory Castle (formerly UNC5221), exploited the flaw as a zero-day from early September 2026. Mandiant describes this sequence of attacks:
- The attackers first broke into BeyondTrust Remote Support appliances.
- They moved on to internal Linux systems, installed SLIMSAVAGE web shells and gained root rights.
- They then scanned the internal network for VMware systems.
- A custom tool called BONESAW exploited the vCenter flaw, created a vCenter Single Sign-On (SSO) administrator account and stole the directory database (
data.mdb). The tool can also extract the SAML signing keys. - With a tool called SAWSNAKE they forged authentication tokens ("Golden SAML"), which bypasses multi-factor authentication.
- They installed further backdoors (CAGEMATCH, BEARBONES, LAZYBONES), reached ESXi hosts and extracted data from virtual machines, including Windows Active Directory database files.
The same advisory fixes four less severe flaws, rated 6.7 to 8.1. Three are in SDDC Manager: an SQL injection, a command injection and a privilege escalation to root. The fourth is a SAML token signature bypass in VMware Tools for Windows. It can only be exploited where Guest Alias mapping is configured, and it stays inside the virtual machine. All four require an attacker who is already logged in or already has privileges.
Who is affected
- vCenter Server 8.0, 9.0 and 9.1. This includes standalone installations and the vCenter inside VMware Cloud Foundation (including the older 5.x line), vSphere Foundation, Telco Cloud Platform and Telco Cloud Infrastructure.
- Older versions. Broadcom no longer evaluates versions that are out of support. It says vSphere 6.5 and 6.7 should be presumed affected, and so should vSphere 7.0. Customers with an extended support contract for 7.0 can request a patch.
- Enhanced Linked Mode makes no difference. Not using it does not protect you.
- SDDC Manager (VMware Cloud Foundation) and VMware Tools for Windows are affected by the four less severe flaws.
Not affected: ESX/ESXi hosts, VMware NSX, VCF Operations, VCF Automation, VMware Workstation and Fusion, and VMware Tools for operating systems other than Windows. None of the flaws allow code to escape from a virtual machine onto the host. If you do not run vCenter, the main flaw does not concern you.
What to do now
- Find your vCenter instances and their builds. The build is shown in the Summary tab of the vSphere Client. With PowerCLI, after
Connect-VIServer, check$global:DefaultVIServer.Versionand$global:DefaultVIServer.Build. - Limit network access to vCenter until it is patched. Allow it only from administration networks or jump hosts, never from the internet. Broadcom says firewall controls can reduce exposure, but they do not replace the update.
- Back up vCenter (file-based backup or snapshot) before you update.
- Install the fixed version listed in VMSA-2026-0009. The sources name vCenter 8.0 U3m and 9.0.2.0200. For the 9.1 branch and for Telco Cloud, see the vendor advisory linked below. Keep in mind:
- The updates are cumulative and cannot be installed with vCenter Quick Patch.
- VMware Cloud Foundation 5.x customers apply vCenter 8.0 U3m through the asynchronous patching process in KB 88287 and update SDDC Manager to 5.2.5.
- Virtual machines keep running during the update. Only management access is interrupted briefly. While vCenter is offline, some encryption operations against a Standard Key Provider (new encryptions, key rotations) are unavailable.
- If you plan to upgrade to VMware Cloud Foundation 9.1.1: installing 8.0 U3m or 9.0.2.0200 blocks that upgrade later. Either upgrade vCenter to 9.1.1 first and apply the security update there, or wait for VCF 9.1.2.
- Update SDDC Manager, if you use it, to 9.1.1.0200 (9.1.x), 9.0.2.0100 (9.0.x) or 5.2.5 (5.x).
- Update VMware Tools in Windows virtual machines to 13.1.5.0 (13.x) or 12.5.5 (12.x and 11.x). For 32-bit Windows, use 12.4.10, which is part of the 12.5.5 release.
- After the update, log in to the vSphere Client, check that the version is correct and that hosts and virtual machines are connected and managed normally.
How to check whether you are affected
- Any vCenter build older than the fixed versions in VMSA-2026-0009 is vulnerable. If you are unsure, Broadcom says to assume the system is vulnerable.
- Mandiant reports attacks since early September 2026. Patching does not remove an attacker who is already inside, so check for traces of compromise, especially if vCenter was reachable from other networks:
- Review the vCenter SSO users and groups, especially the Administrators group, for accounts you did not create.
- Review vCenter logs for sessions as
administrator@vsphere.localat unusual times or from unexpected source addresses since September. - Check internal Linux systems and appliances that can reach vCenter for unknown web shells, new files in web directories and unexplained root activity.
- If you run BeyondTrust Remote Support, check it as well, because Mandiant names it as the entry point of this campaign.
- If you find signs of compromise, involve your incident response team. The attackers can steal the directory database and the SAML signing keys, and with them they can forge valid logins even after the patch. Changing the affected credentials and keys is therefore part of the cleanup.
Update November 21, 2026
The main vCenter flaw now has the identifier CVE-2026-123890: an authentication bypass using an alternate path or channel in the VMware Directory Service, rated 9.8, which lets an unauthenticated attacker with network access to vCenter gain unauthorized access. On 20 November 2026 CISA added it to its catalog of known exploited vulnerabilities, confirming active exploitation. This is the same flaw described above, so the steps in this article cover it: install the fixed vCenter version from VMSA-2026-0009 and check for signs of compromise. US federal agencies must also follow CISA's BOD 26-04 patching guidance and its "Forensics Triage Requirements", or stop using the product if mitigations are unavailable.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-123890
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
More sources (7)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123890
- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
- https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere?e=48754805
- https://thehackernews.com/2026/11/china-linked-hackers-exploit-critical.html
- https://www.heise.de/news/VMware-stopft-attackierte-Sicherheitsluecken-11532009.html
- https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/
- https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html
If you run virtualization hosts, also check
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
PHP fixes critical session flaw CVE-2026-115560 and six other code execution bugs
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13 fix CVE-2026-115560 (CVSS 9.2), a session serializer mismatch that can lead to code execution. The same release fixes six more critical flaws, so every PHP server should be updated.