Science & TechnologyLOT 261120 · 3 min read
Broadcom patches vCenter zero-day after suspected 2-month exploitation
Broadcom patched a CVSS 9.8 VMware vCenter authentication bypass after Mandiant linked Armory Castle to more than two months of exploitation. Four listed builds are fixed.
Key takeaways
- Broadcom's VMSA-2026-0009 fixes CVE-2026-123890, a CVSS 9.8 authentication bypass in vCenter's VMware Directory Service, with no workaround listed.
- Mandiant dates suspected Armory Castle exploitation to early September, more than two months before Broadcom's Thursday patch.
- The chain began with CVE-2026-102764 in BeyondTrust Remote Support and used BONESAW, SAML token forgery, modified Dropbear SSH and a Slack-linked Go implant.
- Fixed builds are vCenter 9.1.1.0200, 9.0.2.0200, 8.0 U3m and VCF 5.2.5.
- vCenter 7.0 has no listed fix after general support ended in October 2025; CISA had not added CVE-2026-123890 to its KEV catalog by Nov. 18.

By Nathan Brooks
Broadcom has patched a critical VMware vCenter Server authentication bypass, CVE-2026-123890, more than two months after Mandiant detected its use by a suspected China-nexus group. The flaw carries a CVSS score of 9.8 and sits in the VMware Directory Service.
Broadcom tracks the fix as VMSA-2026-0009 and lists no workaround; an attacker with network access to vCenter can bypass authentication. The patch arrived on Thursday; the timing is not flattering.
Mandiant, Google's threat-intelligence unit, attributes the observed use to Armory Castle, formerly UNC5221, a group it assesses as China-nexus. Investigators saw the group use the flaw against an internal vCenter server in early September. SecurityWeek put the window at more than two months before the patch.
Broadcom's advisory credits Mandiant with reporting the flaw but does not mention exploitation in the wild. The distinction matters. Broadcom documents the defect and repair, while Mandiant documents its observed use.
How did the intrusion enter vCenter?
Mandiant said the attackers first entered through CVE-2026-102764, a zero-day in BeyondTrust Remote Support. Google covered that entry point in its October report on the same group. The chain then moved into vCenter.
They ran a custom Go tool that Google calls BONESAW, which used CVE-2026-123890 to obtain a session under the account identifier shown in the report as “[email protected].” BONESAW copied the directory database, extracted the SAML signing key and created a new single sign-on administrator account.
A second tool forged SAML tokens, letting the attackers bypass multi-factor authentication. They also installed backdoors, including a modified Dropbear SSH server and a Go implant that used Slack for command and control. The result is closer to a master-key compromise than a single broken password: stolen SAML material enabled forged sessions and a new administrator account.
The server they compromised had already been patched for CVE-2026-59309, a separate vCenter authentication bypass disclosed on July 29. BONESAW carried a July 13 build timestamp, 16 days before that disclosure, but Google cautioned that Go build metadata can be altered.
Google wrote: “The use of three separate specialized sets of malware and two zero-days in the course of a single compromise indicates that there are significant resources supporting ARMORY CASTLE operations.” The finding rests on the specialized tools, token forgery and second zero-day observed within one intrusion.
Which releases contain the fix?
Broadcom lists these fixed builds:
- vCenter 9.1.1.0200
- vCenter 9.0.2.0200
- vCenter 8.0 U3m
- VCF 5.2.5
Fixes for Telco Cloud Platform and Telco Cloud Infrastructure sit in a separate Broadcom knowledge-base article. vCenter 7.0 reached the end of general support in October 2025 and has no listed fix. Customers with extended-support contracts are told to contact Broadcom Support.
The absence of a listed 7.0 fix is a material gap, not a footnote. Extended support offers a contact route, not a stated remediation build.
What should operators do now?
Google urged affected organizations to apply the patches immediately and restrict network access to vCenter appliances. Mandiant CTO Charles Carmakal told SecurityWeek that organizations “should both apply the patches and examine their systems for evidence of compromise.”
Mandiant's account gives forensic teams specific ground to cover: copied directory data, the extracted SAML signing key, a new single sign-on administrator, forged tokens, modified Dropbear SSH and the Slack-linked Go implant. Patch installation alone does not reverse an intrusion already in progress.
CISA had not placed CVE-2026-123890 in its Known Exploited Vulnerabilities catalog as of the agency's Nov. 18 update. The listing status differed for the BeyondTrust entry point, CVE-2026-102764, which CISA added on Oct. 16. The two dates do not change the immediate patching guidance.
Going forward, the fixed 9.x, 8.0 U3m and VCF 5.2.5 deployments have named remediation paths, while vCenter 7.0 operators still depend on Broadcom Support. For vulnerable installations, patch speed and compromise review now matter more than the wording of any catalog.
mlq.ai (Source)
More from Nathan Brooks
Show full bio
Senior reporter covering people, launches and day-to-day practice in Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.
1,142 articles