Skip to main content

EMAIL Info

 INFO:


Subject: Approval request (P2B): urgent VMware vCenter security update (VMSA-2026-0009), then Q4 RHEL 8.10 OS patching and Dell firmware


Hi [Name],


Broadcom has released a critical VMware security advisory, VMSA-2026-0009, that affects our vCenter servers. The main issue, CVE-2026-123890, is a vCenter authentication bypass rated CVSS 9.8. It has been actively exploited since September 2026 and Broadcom lists no workaround. The fix is vCenter 8.0 Update 3m. vCenter 7.0 reached end of general support in October 2025 and no fix is listed for it, so upgrading to version 8 is the only way to resolve it.


The vCenter upgrade, this quarter's RHEL 8.10 OS patching and the Dell firmware updates have now all been applied and tested in our Reference environment.

Because of the urgency of the VMware issue, we would like to request approval through your P2B change control process for the following order:

1. Lab: apply the vCenter update as soon as possible.

2. Production: upgrade vCenter from version 7 directly to 8.0 Update 3m.

3. Then move forward with the Q4 RHEL 8.10 OS patching and Dell firmware updates.

Release notes for reference:

VMware

- VMSA-2026-0009 security advisory: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495

- vCenter 8.0 Update 3m release notes: https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u3m-release-notes.html

RHEL 8.10 OS patching

- Kernel security update (kernel 4.18.0-553.185.1.el8_10): [Red Hat advisory link]

- eMudhra fix, ca-certificates security update RHSA-2026:88550: https://access.redhat.com/errata/RHSA-2026:88550

- RHEL 8.10 release notes: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/8.10_release_notes/index


Dell firmware (PowerEdge R640)

- BIOS 2.28.1 (August 2026): https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=188CW

- iDRAC9 7.00.00.184 (April 2026): https://www.dell.com/support/manuals/en-us/idrac9-lifecycle-controller-v7.x-series/idrac9_7.00.00.184_rn_pub/product-description?guid=guid-eb98cb63-88fa-4903-a846-bf4ea2fae900&lang=en-us

- Dell OpenManage Enterprise 4.8 (used to apply the firmware): https://www.dell.com/support/manuals/en-us/dell-openmanage-enterprise/ome_plugins_rn_major_release_consolidated_4.8/new-features-of-openmanage-enterprise-48

Please let me know if you need any further information to support the change request.


Kind regards,

[Your name]

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/...