Tech Translated

IT Security & Technology Blog

Practical IT insights for Australian businesses. Our team covers cybersecurity advisories, compliance updates, and plain-English explainers on the technology your business relies on, published regularly as the landscape shifts.

VMware vCenter zero-day CVE-2026-123890 security advisory from All IT Services

VMware vCenter Zero-Day CVE-2026-123890 Exploited: Patch Now

Broadcom has patched a critical VMware vCenter zero-day, CVE-2026-123890, that a China-linked espionage crew has been quietly exploiting since early September. If you run vSphere, this is the one that owns your whole estate.

On 19 November Broadcom disclosed and fixed CVE-2026-123890, an authentication bypass in the VMware Directory Service that scores a near-maximum 9.8. Mandiant and Google Threat Intelligence Group reported that a group they call ARMORY CASTLE, previously tracked as UNC5221, had been exploiting it as a zero-day since early September using a custom tool named BONESAW. The flaw leaks a session key over the directory service on TCP port 2012, letting an unauthenticated attacker log in as administrator@vsphere.local with no password at all.

Why this one is so dangerous

vCenter is the control plane for every ESXi host and virtual machine you run. Own it and you own the lot. In this campaign the attackers pulled Active Directory database files straight off guest VM disks, stole the SAML signing key, then forged logins to walk past multi-factor authentication. This is not purely an enterprise problem either. Plenty of mid-sized organisations we work with across Sydney and the Central West, councils, clubs, accounting practices and wealth firms, still run on-premise vSphere, and vCenter is almost always treated as internal-only and left unpatched for months.

Here is the pattern worth sitting up for: in the real Australian environments we see, vCenter rarely faces the internet, so it gets filed under "internal, low risk" and patching slips. But this intrusion did not begin at vCenter. The crew first landed on a separate appliance, then pivoted to an internal Linux server with no endpoint protection, and attacked vCenter from there. Internal-only is not the same as isolated. If anything on your network can reach port 2012, so can an attacker who gets a foothold anywhere else.

What to do now

  • Patch immediately. Update vCenter to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m per Broadcom advisory VMSA-2026-0009. Assume any older build is vulnerable.
  • Hunt, do not just patch. A patch does not evict an attacker already inside. Check for unexpected SSO administrator accounts, new or rotated SAML signing certificates, and SSH being switched on then off on vCenter.
  • Lock down access. Restrict vCenter management interfaces and port 2012 to a tightly controlled admin network, not the whole LAN.
  • Rotate secrets. If you cannot rule out exposure, rotate the vCenter master key, PostgreSQL credentials and the SAML signing key.
All IT Cybersecurity Services: we patch, harden and monitor VMware and vCenter environments so a flaw like this does not sit open for weeks.
Sources VMware vCenter Zero-Day CVE-2026-123890 Exploited in the Wild, Security Online (reporting Mandiant and Google Threat Intelligence Group, Broadcom VMSA-2026-0009)

Frequently Asked Questions

Am I affected if vCenter is not exposed to the internet?

Possibly. The attackers in this campaign reached vCenter from inside the network after compromising another device, not from the internet. If any internal host can reach vCenter on TCP port 2012, treat it as reachable and patch it.

Does patching fix everything?

No. Patching closes the hole but does not remove an attacker who already got in. You also need to hunt for rogue SSO admin accounts, forged SAML certificates and signs of SSH being enabled on vCenter, then rotate any affected secrets.

We outsource our IT. Should we still worry?

Yes, but the action is simple. Ask your provider whether your vSphere environment is patched to VMSA-2026-0009 and whether they have checked for signs of compromise. If they manage your virtualisation, they should be able to answer today.

What is CVE-2026-123890 in plain terms?

It is a flaw that lets someone on your network log into VMware vCenter as a full administrator without a password. Because vCenter controls all your virtual machines, that is about as bad as it gets for a virtualised environment.

Not sure if your virtual environment is patched?

All IT Services can check your VMware and vCenter patch status, lock down management access and hunt for signs of compromise, before someone else does.


Related Guide

Cybersecurity for Sydney SMBs

Explore our complete guide to protecting your business from cyber threats.

Read the Full Guide →