UpdatedCritical severity

VMware vCenter zero-day CVE-2026-123890 patched after attacks since September

Broadcom has fixed a vCenter Server flaw rated CVSS 9.8 that Google says a suspected Chinese state-backed group exploited, after first breaking in through BeyondTrust appliances.

By Mr Elite Published Updated 9 min read

Severity
Critical
Status
Reported by outlets
Sources
3
Last checked

Latest updates

  1. Help Net Security, citing Google Threat Intelligence Group, reports that Broadcom's advisory does not mention the exploitation, that Mandiant CTO Charles Carmakal said multiple incidents were investigated, and that the group appears to have known of the flaw before 29 July. Mandiant is also credited with discovering the flaw, and Google gave extra hardening advice.
  2. The Hacker News reported that CVE-2026-123890 carries a CVSS score of 9.8, a figure the published story does not give. It also describes the attribution to Armory Castle as suspected China-nexus.

The short version

  • Broadcom patched CVE-2026-123890, a vCenter authentication bypass, on 19 November in advisory VMSA-2026-0009. The Hacker News and Help Net Security give its CVSS score as 9.8.
  • Mandiant and Google Threat Intelligence Group say Armory Castle, formerly UNC5221, exploited it from at least early September 2026, more than two months before the fix.
  • Help Net Security reports that Broadcom's advisory does not mention the exploitation and that Broadcom says there are no workarounds.
  • Mandiant says the attackers entered through BeyondTrust Remote Support, then moved to vCenter and ESXi hosts. Mandiant CTO Charles Carmakal said multiple incidents have been investigated.

What happened

Broadcom released security updates on 19 November for a critical authentication bypass in VMware vCenter Server, tracked as CVE-2026-123890. BleepingComputer reported that Chinese-linked hackers have exploited it as a zero-day, meaning before a fix existed, since September 2026.

The Hacker News, publishing on 20 November, gave the flaw a CVSS score of 9.8, and Help Net Security gave the same figure. CVSS is the standard 0 to 10 scale for rating how severe a vulnerability is, and 9.8 sits near the top of it. The Hacker News called the attacker a suspected China-nexus espionage group.

vCenter is the management platform organisations use to run their VMware virtual machines. The flaw sits in the VMware Directory Service. According to Broadcom, an unauthenticated attacker with network access to a vulnerable server can bypass authentication and gain unauthorised access, which can lead to administrative control over the virtual machines it manages.

The fix is in advisory VMSA-2026-0009, which also covers four other vulnerabilities in VMware SDDC Manager and VMware Tools for Windows. Broadcom said any version of vCenter, SDDC Manager or VMware Tools for Windows before the fixed versions is affected, and that there are no workarounds. Help Net Security reported that the advisory makes no mention of exploitation in the wild, and that Broadcom credits Mandiant with discovering the flaw.

Google's Mandiant and Google Threat Intelligence Group (GTIG) attribute the attacks to a suspected Chinese state-sponsored group called Armory Castle, formerly UNC5221. Help Net Security reported that the group has been exploiting the flaw since at least early September. Mandiant CTO Charles Carmakal said in a LinkedIn post that the teams have investigated multiple incidents, and urged organisations to apply the patches and examine their systems for evidence of compromise.

BleepingComputer described Armory Castle as a cyberespionage group known for zero-day attacks on enterprise network appliances, including Citrix NetScaler and Ivanti Connect Secure. Help Net Security said GTIG and Mandiant have tracked the group using zero-days and n-days (known, already patched flaws) against edge and security appliances since 2023. In the intrusion detailed in their report, the group got in through BeyondTrust Remote Support zero-day CVE-2026-102764, which BleepingComputer said has been abused since late August.

Why it happened

Broadcom describes the flaw as an authentication bypass in the VMware Directory Service. It affects vCenter whether or not Enhanced Linked Mode is enabled. The company has not published further technical detail in the material reported so far.

Mandiant describes the attack chain. The group first compromised BeyondTrust Remote Support appliances, then moved sideways into internal Linux appliances. Help Net Security reported that these had no endpoint detection and response (EDR) tools. BleepingComputer reported that the group installed SLIMSAVAGE web shells (small scripts that give remote control through a web server), escalated to root and scanned the internal network for VMware systems.

The attackers then ran a custom Go-language tool, BONESAW, against vCenter. Mandiant said successful exploitation creates an authenticated session as administrator@vsphere.local, after which the attacker can run commands and take files, including the data.mdb directory database, through the vmdird RPC interface vmdirdbcp. Mandiant observed BONESAW creating a Single Sign-On administrator account and copying the database.

Help Net Security adds that the group knew of the flaw before 29 July, when a different vCenter authentication bypass, CVE-2026-59309, was disclosed. Both let an attacker obtain a session key without a password, but Broadcom stresses that CVE-2026-123890 is a new and distinct issue. The BONESAW binary carries a build timestamp of 13 July, though the report notes that Go build metadata can be modified before compilation. Logs show it was run in early September against a server already patched for the older flaw, and Google believes it was likely developed for broader operations.

How this kind of failure works

An authentication bypass means the system lets someone in without checking who they are. Picture an office building where the front desk checks every visitor's badge, but a side door to the server room opens if you knock in a particular way. The lock works as designed for everyone who uses the front desk. The flaw is the path that skips it.

vCenter is an attractive target because one login controls many machines. An administrator session there can reach every virtual machine and host it manages, much as a master key opens every door on a floor. Attackers who reach it can often read data from guests without touching each one separately.

Directory databases and signing keys add a second layer of risk. Mandiant says BONESAW copies the directory database, which holds the key used to sign login tokens, and a second tool, SAWSNAKE, can pull SAML signing keys from it. SAML signing keys are the secrets a system uses to vouch that a login token is genuine. With them, an attacker can forge tokens, an approach called Golden SAML. The researchers wrote that this allows forged tokens, bypassing MFA and impersonating any user.

This also explains why the attackers started elsewhere. Remote support appliances and other edge devices sit at the boundary of a network and are reachable from outside. Many such appliances cannot run EDR software, so intrusions on them can go unseen. Once one falls, internal management systems that were never meant to face the internet become the next step.

Who is affected

Broadcom says affected products are any version of vCenter, SDDC Manager or VMware Tools for Windows prior to the fixed versions in VMSA-2026-0009. That includes standalone deployments and those inside VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform and Telco Cloud Infrastructure. You can check your build numbers against the fixed versions listed in the advisory.

Telling whether you were attacked is harder. BleepingComputer reported that Mandiant named the tools and web shells it saw, including BONESAW, SAWSNAKE, SLIMSAVAGE, CAGEMATCH, BEARBONES and LAZYBONES. Help Net Security reported that the Google report includes indicators of compromise and YARA rules (pattern-matching rules used to hunt for malware). An unexpected SSO administrator account is one sign, since Mandiant observed BONESAW creating one.

Mandiant said the intrusions reached ESXi hosts, where the group pulled the Active Directory database and registry hives off a Windows VM's disk. Help Net Security reported that the files were moved to the BeyondTrust appliance, from which GTIG said the group likely exfiltrated the data. Organisations that ran both an exposed BeyondTrust Remote Support appliance and vCenter have the clearest reason to investigate. The number of victims has not been published.

How to defend against it

Tick each step as you check it. Your progress is saved on this device.

What to learn from this

The concept: Signing keys as crown jewels (Golden SAML)

Single sign-on works because one trusted service signs a token saying who you are, and other systems accept that signature. Whoever holds the signing key can mint tokens for anyone, including administrators. The tokens look genuine because they carry a valid signature.

This is why Mandiant's description of key theft matters beyond the patch. A forged token does not need a password or a second factor, so multifactor authentication offers no protection once the key is stolen.

The same pattern appears in any system built on signed trust, such as certificate authorities, cloud identity providers and code-signing services. Guarding the key, limiting who can read it and being ready to replace it matter as much as guarding the login page.

Patching closes the door the attacker used, but stolen signing keys keep working until you replace them.

Quick check

Sign in to earn 10 XP for a right answer

An organisation patches vCenter after confirming attackers had already stolen its SAML signing keys. What else is needed?

Timeline

  1. 13 July 2026 Help Net Security reported that the BONESAW binary carries this build timestamp, though the report says such metadata can be modified.
  2. 29 July 2026 Help Net Security reported that a different vCenter authentication bypass, CVE-2026-59309, was disclosed. Mandiant has evidence the group knew of CVE-2026-123890 before this date.
  3. Late August 2026 BleepingComputer reported that exploitation of the BeyondTrust Remote Support zero-day CVE-2026-102764 began.
  4. Early September 2026 Mandiant says Armory Castle exploited vCenter flaw CVE-2026-123890 as a zero-day.
  5. 19 November 2026 Broadcom released VMSA-2026-0009, patching the vCenter flaw and four other vulnerabilities.
  6. 20 November 2026 BleepingComputer, The Hacker News and Help Net Security reported Mandiant and Google Threat Intelligence Group's published findings on the attacks.

What is not known yet

  • How many organisations were compromised through CVE-2026-123890 has not been stated.
  • Broadcom's advisory does not mention exploitation, and it has not said whether it knew of the attacks before the patch.
  • Mandiant and GTIG describe the attribution to Armory Castle as suspected, and the group's China link has not been independently confirmed in the reporting.
  • It is not yet clear whether other attackers have found or are using the flaw.

Questions people ask

What is CVE-2026-123890?

It is a critical authentication bypass in the VMware Directory Service of vCenter Server. The Hacker News and Help Net Security give it a CVSS score of 9.8. Broadcom says an unauthenticated attacker with network access can gain unauthorised access and potentially administrative control of the virtual machines vCenter manages.

Is there a workaround for the VMware vCenter flaw?

Broadcom says there are no workarounds. The fix is to install the updates listed in VMSA-2026-0009. Google also advises hardening the vCenter appliance and restricting network access to it.

Who is behind the attacks?

Mandiant and Google Threat Intelligence Group attribute them to Armory Castle, formerly UNC5221, a suspected Chinese state-sponsored group. The attribution is described as suspected. Broadcom's advisory does not mention the exploitation or name any group.

How did the attackers reach vCenter?

Mandiant says they first compromised BeyondTrust Remote Support appliances, then moved into internal Linux appliances and scanned for VMware systems. They then ran a custom tool called BONESAW against vCenter.

Sources

  • BleepingComputer: VMware patches vCenter zero-day exploited in attacks since September
  • The Hacker News: China-Linked Hackers Exploit Critical VMware vCenter Zero-Day to Gain Admin Access and Steal Data
  • Help Net Security: VMware vCenter zero-day exploited for months before patch (CVE-2026-123890)

Know someone who should see this?

Keep reading