VMware vCenter Zero-Day Exploited for Months: Patch and Hunt Now
Broadcom has fixed CVE-2026-123890, a 9.8-rated vCenter authentication bypass that a China-linked group exploited since September. Here is who is affected and what to do.
In this article
Organisations that run their servers on VMware need to treat this one as an emergency. On 19 November 2026, Broadcom released fixes for CVE-2026-123890, a critical flaw in VMware vCenter that lets an attacker with network access log in as the Administrator without any password. Google’s Mandiant team says a China-linked espionage group had been exploiting it for more than two months before the patch existed.
This article is for IT managers, managed service providers and anyone responsible for a VMware environment, including banks, telcos, data centres and larger SMEs across Nigeria and Africa that host their own systems.
What happened
Broadcom’s advisory, VMSA-2026-0009, addresses five vulnerabilities across VMware products. The most serious is CVE-2026-123890, which carries a CVSS score of 9.8 out of 10. It sits in the VMware Directory Service, the part of vCenter that handles identity, and is classed as an authentication bypass through an alternate path.

Mandiant privately reported the bug to Broadcom after investigating several intrusions. It links the attacks to a group it now calls Armory Castle, previously tracked as UNC5221 and also known as Warp Panda. According to Rapid7, in-the-wild exploitation dates back to at least September 2026. Broadcom’s own advisory, SecurityWeek notes, does not mention the active exploitation.
How the attacks worked
Mandiant’s findings, as reported by SecurityWeek, show a careful, multi-stage intrusion:
- The attackers first got in through a recently patched zero-day in BeyondTrust Remote Support (CVE-2026-102764).
- They moved to Linux appliances inside the network, then turned to vCenter in early September.
- A custom tool called Bonesaw exploited CVE-2026-123890, stole vCenter’s internal identity database, extracted SAML signing material and created a single sign-on administrator account.
- A second tool forged SAML tokens, and backdoors were installed. The group also took the vCenter master encryption key and database credentials before moving to an ESXi host.
Two details stand out. Bonesaw worked against a vCenter server that was already patched for CVE-2026-59309, a separate authentication bypass disclosed in July. And Mandiant says the group knew about the new flaw before that July disclosure, which means fully up-to-date systems were still exposed.
Who is affected and the fixed versions
According to Rapid7’s summary of the advisory, the fixed releases are:
- VMware Cloud Foundation / vSphere Foundation 9.1.x: update to 9.1.1.0200
- VMware Cloud Foundation / vSphere Foundation 9.0.x: update to 9.0.2.0200
- vCenter Server 8.0: update to 8.0 U3m
- VMware Cloud Foundation 5.x: update to 5.2.5
- Telco Cloud Platform and Telco Cloud Infrastructure: 8.0 U3m, per Broadcom KB463116
- vCenter Server 7.0: no public patch. Version 7.0 reached end of general support in October 2025, and only extended-support customers should contact Broadcom. Mandiant says Bonesaw works against 7.x and 8.x.
Important practical notes
- Broadcom lists no workaround, and the fix cannot be applied with vCenter Quick Patch. You need a standard update.
- Systems that received the July fix for CVE-2026-59309 still need this update.
- Updating vCenter temporarily takes its management interfaces offline, but Broadcom says running virtual machines and containers keep working.
- The 8.0 U3m and 9.0.2.0200 updates add a “Back-in-Time” restriction that blocks upgrades to VMware Cloud Foundation 9.1.1. If you are mid-upgrade, check Broadcom’s FAQ and interoperability matrix first.
Why it matters beyond VMware
vCenter is the control room for a virtualised data centre. Whoever controls it can switch off, copy or tamper with every server it manages. That is why espionage and ransomware groups target it so often. This campaign also shows a pattern worth learning from: attackers chained a remote support tool, quiet Linux appliances and the virtualisation layer, all systems that often sit outside normal endpoint monitoring.
For organisations in Nigeria preparing to bring payment and customer data onto local infrastructure, the lesson is clear: the management plane of your data centre needs the same patching urgency and monitoring as your internet-facing websites.
What you should do
- Patch as an emergency change, outside normal maintenance windows, using the fixed versions above.
- Plan your way off vCenter 7.0 if you still run it without extended support, and restrict network access to it in the meantime.
- Restrict access to vCenter so only a dedicated management network or jump host can reach it, never the open internet or the general office LAN.
- Hunt for compromise, as Mandiant’s CTO urged. Look for unexpected single sign-on administrator accounts, unusual logins, and changes to identity or SAML configuration since September.
- Rotate secrets if you find signs of intrusion, including SSO signing certificates, the vCenter database credentials and administrator passwords.
- Patch remote support tools too. BeyondTrust and similar products were the entry point here.
- Ask your provider. If an MSP or data centre manages VMware for you, ask in writing when they will patch and whether they have checked for compromise.
Sources
- SecurityWeek: Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT
- Rapid7: CVE-2026-123890 Critical Authentication Bypass in VMware vCenter
Featured image: Photo: “Datacenter Server Racks” by Carl Lender, CC BY 2.0, via Wikimedia Commons — source
Was this article helpful?
adminVerified expert
Cybersecurity Analyst
Federal Capital Territory (Abuja)
Credentials: MCPN, MNCS, IAENG | System Analyst · Web Developer · CEH · CC · CDST
Got expertise to share? Write for us →


