Skip to main content

New Jira - vCenter

 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

  1. Download the 8.0 U3m patch from the Broadcom Support Portal and check its checksum.
  2. 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.
  3. In VAMI, go to Update and stage and install 8.0 U3m.
  4. 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.
  5. 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.
  6. Write up the procedure, timings and any problems in Confluence (draft MOP for customer rollout).
  7. 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

Popular posts from this blog

Nov 17

 INFO: Only one package is missing, and it's my mistake. The command I gave you to check installed packages (in the short runbook) left out python3-unbound . So I wrongly told you no server had it. In fact every B server has python3-unbound , and it must be the same version as unbound-libs . The good news: that's the only problem. Kernel, vim, libtiff, rhc, LVM and GRUB all passed on every server. Fix: Download one more file from Red Hat (RHSA-2026:70754, RHEL 8 x86_64): python3-unbound-1.16.2-5.14.el8_10.4.x86_64.rpm Copy it to the B master: scp python3-unbound-1.16.2-5.14.el8_10.4.x86_64.rpm root@<rbb-ref-b-ansible>:/root/releases/2026.11/extra-rpms/ Step 2 again: answer y to "Use the existing folder" answer y to "Copy them into the repo?" answer y to the commands and to "Carry on" os-patch already points at rhel-8-10-nov2026 , so nothing changes there. Step 3 again. Every B server except vlim06 should show OK . v...

New Command 3

 INFO: These results are almost identical to the last run, which tells us the servers were still checking against an old copy of the repo list. Two things caused that. The B master is still running the old script. The message reads "dnf reports a conflict. Run: dnf update --assumeno", which is the 1.4 wording. Version 1.4.1 would also print dnf: lines underneath. The servers reused yesterday's repo list. When dnf reads a repo, it keeps a copy of the package list and reuses it for up to 48 hours. So the B servers checked against the list from before you added the 8 AppStream RPMs, and couldn't see them. That's why vlim03 still asks for perl and gcc. I've fixed the second one in the script: version 1.4.2 makes the dry run read the repo fresh every time. I've attached the script, the README (Word and PDF) and the pseudocode, all updated. Next steps: Copy os_patch_wizard.sh v1.4.2 to rbb-ref-b-ansible , replacing the old one. Check it with: grep...

New A Run

 INFO: You're in good shape at 5.8 GB free. The tar file can go straight from where it is. dbv6admin can already read /var/www/html/rbb-rhel8-repo-20261117.tar.gz , so it doesn't need copying to /tmp on B first. Only extra-rpms (160 MB) has to go through /tmp , because dbv6admin can't get into /root . On B, as root 1. Put extra-rpms where dbv6admin can reach it, and take the tar file's fingerprint cp -r /root/releases/2026.11/extra-rpms /tmp/ chown -R dbv6admin:dbv6admin /tmp/extra-rpms cp /root/os_patch_wizard_1.5.2.sh /tmp/ chown dbv6admin:dbv6admin /tmp/os_patch_wizard_1.5.2.sh sha256sum /var/www/html/rbb-rhel8-repo-20261117.tar.gz exit Write down the code sha256sum prints. You'll compare it on A. Skip the two wizard lines if A already has 1.5.2. To check, run grep SCRIPT_VERSION= /root/os_patch_wizard*.sh on A. On B, as dbv6admin 2. Send everything to A's /tmp scp /var/www/html/rbb-rhel8-repo-20261117.tar.gz dbv6admin@<A-master>:/tmp/ scp -r /tmp/...