The Keys to the Whole House: What the vCenter Bypass Teaches Us About Management Planes

Thursday, November 19. Broadcom publishes VMSA-2026-0009, a Critical advisory for VMware vCenter. The same day, Mandiant drops a blog saying a suspected espionage group had already used the bug back in early September. By Friday, November 20, CISA has CVE-2026-123890 in its Known Exploited Vulnerabilities catalog.

Mira, this one deserves your weekend. Not because it’s a VM escape or remote code execution. It’s neither. It matters because vCenter is the control plane for your virtual estate, and this bug lets someone walk past the front desk and get handed an admin badge.

What actually happened

Let’s start with the vendor, in its own words. Broadcom says “VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service.” The attack vector: “A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system.”

Severity is Critical, CVSSv3 9.8: network attack, no privileges, no user interaction. CISA’s KEV entry spells it out as a bug that “allows an unauthenticated attacker with network access to vCenter to bypass authentication.” Unauthenticated is CISA’s word; Broadcom’s prose says network access and bypass.

Notice what Broadcom does not say. The advisory never uses “exploited in the wild” or “zero-day.” It thanks Mandiant “for reporting this issue to us.” The exploitation story comes from Mandiant and CISA’s KEV listing.

Here’s Mandiant’s attribution, exactly: “GTIG attributes this activity to the suspected PRC-nexus espionage actor ARMORY CASTLE (formerly tracked as UNC5221).” No confidence grade in the post. Suspected is the word, amigos. If you see a headline calling it a “Chinese APT,” that’s press wording, not Mandiant’s.

Mandiant says ARMORY CASTLE “exploited this vulnerability in early September 2026 using BONESAW, according to forensic evidence.” Early September is all we get. No calendar day.

Now the part I want you to sit with. This was not an internet-facing vCenter getting popped. In the intrusion Mandiant documented, the actor first owned a BeyondTrust Remote Support appliance. Mandiant’s October 15 post says ARMORY CASTLE exploited that BeyondTrust bug, CVE-2026-102764, as a zero-day in late August 2026. From that remote support box, the actor moved laterally to an internal Linux appliance, and from there reached vCenter. The vCenter bug was a post-compromise tool.

Once in, Mandiant describes the actor creating an SSO administrator account, stealing the vCenter master crypto key and database password file, and logging into ESXi hosts. Those are Mandiant’s incident findings, not VMSA statements.

Keep it straight: Broadcom’s FAQ says ESX is not affected and this is not a VM escape. The other four CVEs in the same VMSA are separate issues.

Why it matters for critical infrastructure and OT (my analysis)

Up front, familia: no source I have names an OT, ICS, or SCADA victim for this CVE. None. What follows is my analysis, not a reported incident.

Here’s why I still care. In a lot of plants, the engineering workstations, the historian, the virtualized SCADA or HMI servers, and the jump hosts all live on vSphere. vCenter is the building manager’s master key ring. You don’t need to break the locks on each apartment (the hypervisor) if someone hands you the ring at the front desk. Broadcom says ESXi isn’t the vulnerable part, claro, but an admin session on vCenter still reaches every VM it manages.

Second, look at the path Mandiant documented. A remote support appliance at the edge, then an internal Linux box, then the management plane. Third-party and vendor remote access is exactly how a lot of OT networks get touched. Mandiant doesn’t call this victim industrial, but anyone who has approved a vendor session into a plant knows that pattern.

Third, “network access to vCenter” is a low bar once someone is already inside. If your vCenter is reachable from a flat corporate VLAN, every compromised laptop is a candidate starting point. NIST SP 800-82r3 talks about using a DMZ architecture “to prevent network traffic from passing directly between the corporate and OT networks,” and about “having separate authentication mechanisms and credentials” for corporate and OT users. That’s the design I’d want around a vCenter that manages plant VMs.

Good news for patch planning: Broadcom’s FAQ says updating vCenter does not stop running VM workloads. Your historian keeps running, so “we can’t take downtime” gets a lot weaker, entiendes.

What I’d do this week

  1. Find every vCenter. Include the ones inside VMware Cloud Foundation, vSphere Foundation, and Telco Cloud stacks. Broadcom’s FAQ says if you’re unsure whether you’re affected, it’s likely you are.
  2. Patch to the fixed build in the VMSA. From the Response Matrix: vCenter 9.1.x.x to 9.1.1.0200. vCenter 9.0.x.x to 9.0.2.0200. vCenter 8.0 to 8.0 U3m. VMware Cloud Foundation vCenter 5.x to 5.2.5, with the async patching guide in KB88287 (the FAQ says VCF 5.x applies vCenter 8.0 U3m that way and updates SDDC Manager to 5.2.5). Telco Cloud Platform and Telco Cloud Infrastructure: follow KB463116. Patches are cumulative. These updates aren’t eligible for Quick Patch.
  3. Deal with 7.0 honestly. There is no public fixed build. Broadcom says to contact support if you have an extended support contract. vSphere 7 reached End of General Support on October 2, 2025. Asked whether 6.5 or 6.7 is affected, Broadcom says “Presume that it does.” Por favor, put the upgrade on the calendar.
  4. Don’t wait for a workaround. The VMSA lists Workarounds: None. Firewalls and other compensating controls are your call, not Broadcom’s.
  5. Shrink who can reach vCenter. CISA tells you to evaluate internet exposure. Mandiant goes further and warns the default appliance firewall “lacks the precision required for a Zero Trust model.” Put vCenter in a tight management zone and test reachability from the OT side, not just from IT diagrams. That’s Mandiant hardening and my analysis, not a vendor workaround.
  6. Hunt, because patching isn’t the end. Mandiant published IP addresses, file paths, and YARA rules. Run them. Look for unexpected SSO admin or local admin accounts, SSH being switched on and off on the appliance, and odd ESXi Host Client or root SSH logins. KEV marks forensic triage as Yes for this one.
  7. Pull the thread on remote access. If you run BeyondTrust Remote Support, treat CVE-2026-102764 and Mandiant’s October 15 post as part of the same campaign. Review every vendor remote access path that lands inside your network.

For federal civilian agencies, the KEV due date is November 23, 2026, under BOD 26-04. Everyone else, take the hint. KEV lists known ransomware campaign use as Unknown, so I won’t tell you ransomware crews are using this.

Bottom line

  • This is an unauthenticated authentication bypass in vCenter, CVSS 9.8, with no workaround. Patch to the VMSA builds and plan 7.0 now.
  • Mandiant documented it as a post-compromise move after a remote support appliance, so internal reachability to vCenter matters as much as internet exposure.
  • If vCenter manages your plant VMs, it’s part of your OT attack surface. Zone it, hunt it, and test it from the OT side.

Stay sharp out there.

Javier

Sources

  1. https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
  2. https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md
  3. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
  4. https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
  5. https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-123890
  6. https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere
  7. https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-beyondtrust/
  8. https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-82r3.pdf

Leave a Reply