China-linked intruders exploited vCenter Server auth bypass zero-day
High · BleepingComputer ·
Exploited
Verification: The core patch and exploitation claim is plausible, but the excerpt's 'since September 2026' timeline is future-dated and therefore inconsistent and unverifiable.
Key points
- Attackers linked to China used a vCenter Server authentication bypass in zero-day intrusions.
- Broadcom/VMware published fixes in September 2026.
- No CVE identifier was included in the available facts.
- Virtualization admins should patch, restrict management access, and review logs now.
In September 2026, Broadcom's VMware business disclosed that its vCenter Server product had an authentication bypass that was already being used in intrusions. The attackers are described as having ties to China. The flaw let intruders get past login checks without valid credentials, and exploitation happened before a fix was available. Broadcom and VMware have since published updates.
vCenter Server is the management hub for VMware virtual estates. A compromise there can expose hypervisor controls, virtual machine inventories, datastores and administrative credentials. Organizations running vCenter are affected, particularly any instance reachable from the internet or placed on flat networks. K-12 and government agencies often depend on virtualization for daily operations, so a management-plane bypass is a high-impact event.
The facts do not name victims, the exact intrusion group, or a CVE identifier. That absence matters for detection teams: they cannot rely on a CVE-specific signature alone. Defenders should use vendor guidance and behavior-based monitoring. The timing—September 2026—means patch windows and incident-response playbooks should be reviewed immediately.
Management interfaces are frequent targets because they concentrate power. An attacker who bypasses authentication can create or alter virtual machines, reach datastores, and move toward other systems. Zero-day use shortens the defender's window to react. Even without a CVE, the combination of a central management product and pre-patch exploitation warrants urgent action.
Watch for vendor advisories, updated indicators, and reports of follow-on activity. Review vCenter and SSO logs for unusual logins, new administrative accounts, unexpected API calls, and VM or snapshot changes. Restrict management access, segment networks, and rotate credentials that may have been exposed.
What to do now
- Apply the latest vCenter Server update from Broadcom/VMware immediately; treat internet-facing instances as urgent.
- Remove vCenter management interfaces from direct internet exposure; require VPN or jump host access and restrict source IPs.
- Audit vCenter and SSO logs for authentication anomalies, new admin accounts, unusual API calls, and VM snapshot or export activity.
- Rotate credentials and secrets that could be exposed by vCenter, including service accounts and ESXi/vCenter admin passwords.
- Review vCenter permissions and remove unnecessary admin or SSO privileges; enable MFA where supported.
- Segment management networks from user and workload networks, and monitor east-west traffic to hypervisors.
- Track Broadcom/VMware advisories and threat intelligence for updated indicators; no CVE was provided, so rely on vendor guidance.
Original source
Original AI-assisted analysis, sources cited. Verify with the vendor advisory before acting.