Administrator Without a Password: The VMware vCenter Auth Bypass a Chinese APT Rode for Months

A flaw in vCenter's identity layer lets anyone with network access become Administrator without a password, and Google's Mandiant says a China-nexus group quietly exploited it as a zero-day since September to deploy backdoors. Broadcom's emergency patch is out. Here's the chain, who's exposed, and how to hunt.

4 min readAdvanced

Executive summary. CVE-2026-123890 is a critical (CVSS 9.8) authentication bypass in VMware vCenter's Directory Service. An attacker with network access and no credentials can bypass authentication and gain access as the Administrator user, full control of the virtualization control plane. Broadcom shipped the fix in VMSA-2026-0009 on 19 November 2026. Google's Mandiant attributes exploitation to the China-nexus group ARMORY CASTLE, which it says used a custom Go tool, BONESAW, to exploit the flaw as a zero-day since early September 2026 and deploy backdoors for espionage (Broadcom's advisory itself does not confirm exploitation, and KEV status was unresolved at the time of writing). Crucially, Broadcom's FAQ says every vCenter below the fixed builds needs the update, even systems that already received the earlier CVE-2026-59309 fix. There is no workaround. If you run vCenter, patch now and hunt back to September.

VMware vCenter CVE-2026-123890 authentication bypass chain

What it is

Field Detail
CVE CVE-2026-123890 (distinct from CVE-2026-59309)
Product VMware vCenter — the Directory Service
Type Authentication bypass → access as Administrator
Severity 9.8 Critical
Access Network, unauthenticated
Exploited Attributed to ARMORY CASTLE (China-nexus) via BONESAW, since ~Sept 2026 (per Mandiant)
Fixed VMSA-2026-0009 (vCenter 9.1.1.0200, 8.0 U3m, VCF 5.2.5); no workaround

Why vCenter is the crown jewel

vCenter manages ESXi hosts and every virtual machine in an environment. Administrator on vCenter means:

  • Control of all VMs: power, snapshot, clone, export, console access, and the data inside them.
  • Control of the hosts: deploy to ESXi, and from there the guests.
  • Access to credentials and configuration vCenter stores, and to backup and management integrations.

That's why nation-state actors prize it: one bypass yields the whole estate. It sits alongside this month's other control-plane compromises (Xen Orchestra, N-central, ScreenConnect) in a clear pattern, attackers are going after the systems that manage everything else.

The chain

  1. Network reach to a vCenter server (no credentials).
  2. Authentication bypass in the VMware Directory Service (the identity component).
  3. Access granted as the Administrator user.
  4. In the observed campaign: deploy a backdoor (via the BONESAW tool) for persistent, quiet access, classic espionage tradecraft.

Because it's a flaw in the identity layer itself, there's no credential to steal or brute-force; the check is simply bypassed.

The patch nuance that will catch people out

Broadcom's FAQ is explicit: applying the earlier CVE-2026-59309 fix does not protect you from CVE-2026-123890. Teams that patched vCenter recently may assume they're covered, they're not. Every vCenter below the VMSA-2026-0009 fixed builds needs this update, and there is no workaround to fall back on.

Remediation

Now

  1. Patch vCenter to the fixed builds in VMSA-2026-0009 (reported as 9.1.1.0200, 8.0 U3m, VCF 5.2.5 — confirm against the advisory for your line).
  2. Restrict network access to vCenter management interfaces to a management network / jump host while you patch. It should never be broadly reachable.
  3. Treat any internet- or widely-exposed vCenter as a priority and a candidate for compromise given the September exploitation window.

Then

  1. Hunt back to early September (see below) — this was a zero-day for months.
  2. Rotate vCenter credentials, SSO/identity secrets, and any secrets vCenter integrations hold if you find indicators.

Detection and hunting

Assume a long dwell time. Look at the control plane and the hosts.

Where Look for
vCenter / SSO logs Administrator sessions without a corresponding login; logins from unfamiliar IPs; new admin accounts or roles
Appliance New processes, services, cron/systemd units, SSH keys on the vCenter appliance; unexpected binaries (e.g. Go tooling)
ESXi hosts New VIBs, SSH enabled unexpectedly, rogue VMs, snapshots/exports you didn't initiate
Network New outbound connections from vCenter/ESXi; traffic to unfamiliar infrastructure
Timeline Anomalies from early September 2026 onward, not just recent days

Conclusion

CVE-2026-123890 is a textbook high-value target: an unauthenticated bypass to Administrator on the system that runs your entire virtual estate, exploited quietly for months by a capable actor. The patch is out with no workaround, and the earlier fix doesn't cover it, so the job is to patch to VMSA-2026-0009, restrict access, and hunt from September.

Do this now: patch vCenter to the VMSA-2026-0009 builds (even if you applied the earlier fix), lock management access to a trusted network, and hunt the control plane and ESXi hosts back to early September.

Related: Xen Orchestra auth bypass and The Collapsing Patch Window.

Sources: SecurityWeek, Google Cloud / Mandiant (ARMORY CASTLE), Rapid7, BleepingComputer, The Hacker News. Exploitation attribution is Mandiant's; Broadcom's advisory does not confirm it. Confirm fixed builds against VMSA-2026-0009.

HackersRoot Research · Research team

The HackersRoot research team investigates attack techniques across AI systems, cloud and identity, and enterprise networks, then publishes the detections and hardening guidance that stop them.

More from HackersRoot →

Related research