VMware vCenter Zero-Day: How to Patch CVE-2026-123890 and Check for Intrusions

Attackers exploited a critical vCenter authentication bypass before its fix. Check affected versions, patch and investigate for rogue accounts and stolen keys.
Server racks in a data center used to illustrate enterprise networking and security systems
Photo by Kevin Ache on Unsplash

Broadcom has patched a critical VMware vCenter Server authentication bypass that attackers used as a zero-day in September, according to Google’s Mandiant incident-response team. The flaw, CVE-2026-123890, can give an attacker with network access an administrative session without a password.

The November 19 Broadcom advisory lists fixes for supported releases and no official workaround. Administrators should inventory vCenter appliances, apply the appropriate update promptly and investigate exposed systems: patching closes the flaw but does not remove an account or key an intruder may already have obtained.

Which vCenter versions need attention?

vCenter centrally manages ESXi hosts and their virtual machines, making its management plane a valuable target. Broadcom rates the Directory Service flaw 9.8 out of 10. Its published fixes include:

  • vCenter 8.0: 8.0 Update 3m.
  • vCenter 9.0 and 9.1: 9.0.2.0200 and 9.1.1.0200, respectively.
  • VMware Cloud Foundation 5.x: 5.2.5, with the advisory linking to the async patching guide.
  • vCenter 7.0: Broadcom directs customers with an extended support contract to contact support.

Deployments bundled with Telco Cloud products have separate instructions in the response matrix. Check the current matrix for the exact product and upgrade path; do not assume an ESXi host update also updates its vCenter appliance. The same bulletin addresses separate flaws in SDDC Manager and VMware Tools for Windows, each with its own affected products and fixes.

How the attack reached the management plane

In an investigation published November 19, Mandiant and Google Threat Intelligence Group attributed the observed activity to ARMORY CASTLE, a suspected China-linked espionage group. The researchers describe an intrusion that began with a separate BeyondTrust Remote Support zero-day, then moved through an internal Linux appliance to vCenter. An appliance being inaccessible from the public internet therefore does not eliminate risk from an already-compromised internal system.

The vCenter weakness exposes a session key through the Directory Service’s remote procedure call interface. Mandiant observed a tool it calls BONESAW use that access to establish an administrator session, extract the directory database and create a single sign-on administrator. The tool could also extract a token-signing key, allowing forged authentication assertions. Mandiant observed exploitation against a server that had already been patched for the earlier CVE-2026-59309; that earlier update is not a fix for this vulnerability.

Patch, then investigate possible access

  1. Inventory and update. Identify each vCenter instance, its version, support status and management network. Apply Broadcom’s matching fix and verify the appliance reports the expected build afterward. Coordinate Cloud Foundation updates with the vendor’s documented sequence.
  2. Limit management access. Restrict vCenter management interfaces to approved administrative systems and review internal as well as external paths. Mandiant identifies TCP 2012 as part of the observed exploit path. Network restrictions reduce exposure but are not a substitute for the patch; test changes to avoid disrupting legitimate services.
  3. Review activity and accounts. Preserve available logs and look for unexpected SSO administrators, privilege changes, access to the management interfaces and unexplained SSH enablement. Mandiant’s report provides observed file indicators, detection rules and a detailed timeline to guide a hunt; absence of a named file does not rule out a compromise.
  4. Escalate suspected compromise. Engage incident responders before deleting artifacts. Assess potentially exposed signing keys, credentials, hosts and virtual machines, and follow vendor-supported recovery procedures. Simply changing an administrator password may not invalidate every persistence method described in the investigation.

Mandiant also describes a hardening and logging tool for the vCenter appliance, but advises testing and formal change control before production use. Teams should validate any firewall or logging changes against their own management dependencies and support requirements.

Leave a Reply

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

Previous Post
Signal Messenger logo

Signal Blocks AI Screen Reading: How to Check Your iPhone and Android Settings

Related Posts