Match the fixed version to the component
The vCenter response matrix lists 9.1.1.0200 for the 9.1 branch, 9.0.2.0200 for 9.0, and 8.0 U3m for 8.0. Customers with vCenter 7.0 and extended support are directed to Broadcom Support. The advisory lists no workaround.
These are vCenter targets, not interchangeable version numbers for every product in a Cloud Foundation deployment. Administrators should use the component-specific rows and linked instructions rather than treating one installed update as proof that the whole environment is covered.
The advisory is broader than vCenter, but is not a VM escape
Broadcom’s FAQ distinguishes three SDDC Manager issues from the Windows VMware Tools SAML-signature issue. For SDDC Manager it lists 9.1.1.0200, 9.0.2.0100 and 5.2.5 by branch. Windows Tools fixes include 13.1.5.0 and 12.5.5; the FAQ also identifies the 32-bit Windows package.
The vendor explicitly says this advisory does not describe a guest-to-ESX escape, and ESX itself is not affected by this VMSA. The Tools issue remains inside a Windows guest and has specific prerequisites. Those boundaries prevent a serious management-platform vulnerability from being misrepresented as an unrestricted hypervisor escape.
Mandiant describes attacks that predate disclosure
Mandiant and Google Threat Intelligence Group attribute observed exploitation in early September to ARMORY CASTLE, a suspected China-linked actor. Their report describes BONESAW activity against a vCenter already patched for the separate CVE-2026-59309. An older fix therefore does not establish protection against the newly disclosed flaw.
The investigation connects compromised directory data and signing material with later SAML token abuse. It provides hunting indicators and detection rules. This is evidence reported from investigated intrusions; it does not establish that every exposed deployment is compromised or that the attacker identity has been independently proven by this publication.
Plan an emergency change with upgrade-path checks
Rapid7’s response guidance characterizes this as an emergency vCenter update and highlights that Quick Patch cannot apply these fixes. It also flags a Back-in-Time restriction: the 8.0 U3m and 9.0.2.0200 updates can block an upgrade to Cloud Foundation 9.1.1. Teams already mid-upgrade should review the vendor’s current interoperability guidance.
Broadcom says vCenter management interfaces become temporarily unavailable during updating while running workloads continue. Our assessment: record each component’s before-and-after version and separate patch completion from incident investigation. A successful update removes a known exposure; it is not evidence that earlier unauthorized accounts or stolen signing material have been addressed.

Discussion.
Your perspective matters. Sign in, pick a nickname and choose your cyber identity.
Loading discussion…
Your account name, email and photo stay off your comments.