INFO:
Here's the updated ticket. The v7 status line is new, the Acceptance list is shorter, and the advisory link now sits in the Brief.
Title: Security – Apply VMSA-2026-0009 vCenter Patch (8.0 U3m) to Reference Environment
Brief
Broadcom has published VMSA-2026-0009, a Critical (CVSS 9.8) advisory. Its main bug, CVE-2026-123890, lets someone who can reach vCenter over the network log in as an administrator without a password. Google/Mandiant report that attackers were already using this bug before the patch came out, so it should be treated as urgent. There is no workaround, so patching is the only fix.
This ticket covers updating vCenter in our v8 Reference Environment to 8.0 U3m, checking that everything still works, and recording the steps so the same process can be repeated on customer systems.
Description
In scope
- vCenter Server. Upgrade from the current 8.0 build to 8.0 U3m. Record the current build number before starting.
- VMware Tools on Windows VMs, if we have any. CVE-2026-123894 is fixed in VMware Tools 13.1.5.0 for 13.x, and in 12.5.5 for 12.x and 11.x. RHEL/Linux guests are not affected.
Out of scope
- ESXi hosts. Broadcom confirms ESXi is not affected by this advisory, so no host patching is needed.
- SDDC Manager CVEs (-123891/2/3). These only apply to VMware Cloud Foundation, which we don't run.
v7 status: vCenter 7.0 is affected, but Broadcom has published no public patch, because vSphere 7 general support ended in October 2025. A fix is only available through an extended support contract. Otherwise the remedy is upgrading to 8.0 U3m. Any v7 systems need a separate follow-up ticket.
Steps
- Download the 8.0 U3m patch from the Broadcom Support Portal and check its checksum.
- Back up vCenter in two ways: a file-based backup from the VAMI page (https://<vcenter>:5480) and an offline snapshot of the vCenter VM. If vCenters are linked (Enhanced Linked Mode), snapshot them all at the same time.
- In VAMI, go to Update and stage and install 8.0 U3m.
- After the update, confirm the new build number, that all services are running, that the vSphere Client works, and that hosts and VMs show as connected.
- Do a quick compromise check. Look for SSO administrator accounts nobody on the team created, and check whether SSH on vCenter was turned on and off without a known reason.
- Write up the procedure, timings and any problems in Confluence (draft MOP for customer rollout).
- Remove the snapshot once vCenter has been confirmed stable.
Impact: The vSphere Client and other vCenter management access will be down for a short time during the update. Running VMs are not affected.
Reviewer
- VMware/Infrastructure SME
- Security lead
Acceptance
- vCenter on 8.0 U3m, with all services, hosts and VMs healthy
- Windows VMware Tools updated, or confirmed as not applicable
- Compromise check done and recorded on this ticket
- Procedure documented in Confluence as the customer MOP
Reference
Comments
Post a Comment