HIGHLIGHT OF THE DAY · CYBERSECURITY
Exploited VMware vCenter flaw demands emergency updates and checks for pre-patch intrusions
Broadcom has released fixes for a critical vCenter authentication flaw that Mandiant says attackers exploited before disclosure. Administrators need to verify component versions and investigate earlier access: patching does not remove accounts or SSH keys an intruder already created.
· 4 min read · 9 sources
Briefing24 · AI-assisted research and analysis · Methodology
New fixes address an already exploited authentication flaw
Broadcom released updates on November 19 for CVE-2026-123890, a critical VMware vCenter authentication vulnerability rated 9.8, with no workaround listed. Google/Mandiant published its investigation the same day and says it handled multiple incidents involving exploitation before fixes became available. Broadcom classifies the remediation as an emergency change, giving administrators both a reason to accelerate patching and an available remediation path. [1][3][4][5]
The November 20 revision, VMSA-2026-0009.1, clarifies affected VMware Tools versions. It does not announce additional vCenter exploitation or a larger victim population. This flaw is also distinct from the earlier CVE-2026-59309 authentication bypass: Broadcom says installations below the newly fixed versions need this update even if administrators applied the previous patch. [1][4]
The intrusion reached ESXi through compromised management access
Google describes attackers moving from a compromised BeyondTrust Remote Support appliance through an internal Linux appliance into vCenter. Their BONESAW utility exploited the directory-service flaw, created an SSO administrator account and extracted the directory database. The attackers then stole vCenter cryptographic material and database credentials, reached ESXi, added a root SSH key and extracted files from a guest virtual disk. Google attributes the activity to ARMORY CASTLE, formerly UNC5221, a suspected China-linked espionage actor. [3]
Mandiant places exploitation in early September 2026. BONESAW's July 13 build timestamp does not establish July attacks because build metadata can be altered. The malware analysis also describes SAML signing-key extraction and forged-token capabilities in BONESAW and SAWSNAKE. Those capabilities should not be treated as proof that every such action occurred in the documented intrusion. [3]
Exploitation requires access to vCenter TCP port 2012. The defensive inference is that removing public exposure alone is insufficient when a compromised internal appliance can reach that service. This is not a virtual-machine escape: Broadcom says ESX itself is unaffected by this advisory. The reported route into hosts and guest data was compromised management access. [4][5]
Verify the installed vCenter component, not just the suite release
Broadcom identifies fixed versions 9.1.1.0200 for VCF and vSphere Foundation 9.1.x, and 9.0.2.0200 for their 9.0.x lines. Standalone vCenter 8.0 requires 8.0 U3m. vCenter 7.0 is affected; customers with extended support must contact Broadcom Support rather than assume an ordinary update route is available. [1]
VCF 5.x requires component-level checking and the applicable asynchronous patching process to reach vCenter 8.0 U3m. For VCF 5.2 and 5.2.1, Broadcom specifies the in-product Flexible BOM mechanism, not the Async Patch Tool. A suite release number is therefore not adequate evidence that the installed vCenter component contains the fix. [4]
Broadcom's separate guidance also identifies vCenter 8.0 U3m for Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2, plus Telco Cloud Infrastructure 3.0. Unlisted or extended-support configurations need vendor guidance. [6]
Emergency maintenance has compatibility constraints
These updates are not eligible for vCenter Quick Patch. Broadcom says management access becomes temporarily unavailable during maintenance, although running virtual-machine and container workloads continue. After updating, administrators should verify the installed version in the vSphere Client's Summary tab rather than relying solely on the completion of an update task. [4]
Administrators already moving between releases must also check upgrade compatibility. Broadcom warns that vCenter 8.0 U3m and 9.0.2.0200 introduce a Back-in-Time restriction that blocks upgrades to VCF 9.1.1. The practical implication is to review the supported sequence before scheduling changes, without treating that planning requirement as evidence that remediation can safely wait. [4]
A successful update does not establish a clean environment
Censys recommends looking for unexpected SSO administrators, management-API changes that enabled SSH and unauthorized SSH keys on ESXi. An attacker-created account or key is not removed by installing the security update. Historical evidence matters: the reported attackers disabled SSH again after using it, so finding SSH disabled today does not establish that it was never used. [7]
Mandiant's guidance emphasizes management-network segmentation, dedicated administrative workstations, outbound restrictions and remote logging. Its hardening script is not a risk-free shortcut: the accompanying guidance warns about lockout, backups and possible supportability consequences. Test changes and retain console recovery access. Taken together, the incident and defensive guidance support treating patch deployment and compromise investigation as separate tasks, not interchangeable measures of recovery. [2][3][7]
Independent exposure research does not establish campaign size
The sources provide different kinds of evidence. Broadcom is the primary authority for the vulnerability and fixes; Google/Mandiant supplies the firsthand intrusion investigation. Censys contributes independent internet observations, not independent confirmation of those intrusions. SecurityWeek and Rapid7 largely trace their exploitation accounts to Mandiant, so their reporting should not be counted as separately observed campaigns. [1][3][7][8][9]
Censys reported 1,194 vCenter web properties, a measurement that includes hostname-and-port combinations rather than necessarily unique servers or organizations. It does not show how many expose port 2012, remain vulnerable or were compromised. Its November 19 advisory identified no public exploit code for this CVE. That finding does not negate private exploitation, and code for the earlier vCenter flaw should not be conflated with this vulnerability. [7]
SecurityWeek noted that Broadcom's bulletin omitted in-the-wild exploitation. That omission is not a denial of Mandiant's findings. The central unresolved question is scale: the reviewed disclosures establish prior exploitation, but do not quantify the campaign's overall victim population. [2][5]
Watch for substantive advisory changes and wider incident evidence
The next meaningful developments would be changes to affected-version or remediation guidance, independently documented intrusions, or evidence clarifying campaign reach. Public exploit availability would also merit attention, but administrators already have evidence of private exploitation. For now, the supported priorities are to reach a fixed build, restrict access to the management service and investigate whether attackers established access before the update. [1][3][4][5][7]
Sources & further reading
- Support Content Notification - Support Portal - Broadcom support portal ↗support.broadcom.com
- vSphere and BRICKSTORM Malware: A Defender's Guide | Google Cloud Blog ↗cloud.google.com
- ARMORY CASTLE Exploits vSphere | Google Cloud Blog ↗cloud.google.com
- vcf-security-and-compliance-guidelines/security-advisories/vmsa-2026-0009/README.md at main · vmware/vcf-security-and-compliance-guidelines · GitHub ↗github.com
- ⚠️ URGENT: Critical vulnerability in VMware vCenter exploited for over 2+ months by a suspected PRC-nexus threat actor before today's patch release Mandiant (part of Google Cloud) and Google Threat… | Charles Carmakal ↗www.linkedin.com
- knowledge.broadcom.com ↗knowledge.broadcom.com
- Nov 19 Advisory: VMware vCenter Authentication Bypass [CVE-2026-123890] - Censys ↗censys.com
- VMware vCenter CVE-2026-123890 Zero-Day Exploited - SecurityWeek ↗www.securityweek.com
- CVE-2026-123890: Critical Authentication Bypass in VMware vCenter ↗www.rapid7.com
Researched, written and checked with GPT-6 Astra. Publication is automatic after source, structure and model review checks. These checks can miss errors and do not constitute human verification.
Report a correction · Browse highlights · Read the daily briefing