Critical

VMSA-2026-0009.1 — Patch vCenter to 9.1.1.0200, 9.0.2.0200 (build 25901331) or 8.0 U3m (VCF 5.x: 5.2.5 via KB 88287; Telco Cloud: KB 463116; 7.0 only with extended support).

Details →

Latest News from the Web

Weekend edition · archive

Nothing new shipped from Broadcom since Friday: no new VCF 9.1.1 patches, no new KBs worth your time and no new Terraform or Packer releases. That makes it a good weekend to get ahead of your next vCenter upgrade, so today's deep dive walks through Reduced Downtime Upgrade, what it needs from you in VCF 9.1, and the traps that catch people out.

There's no new VMSA, and if vCenter CVE-2026-59310 isn't patched yet it's still the one to do first, with SDDC Manager still waiting for its Brotli fix.

Elsewhere it's a catch-up weekend: Virtually Speaking's KubeCon episode is the newest podcast, and VMware Explore on Tour London is on Wednesday.

This is an earlier briefing. Read today's Latest Tech News →

  • Security No new VMSA vCenter CVE-2026-59310 is still the priority
  • Releases & KBs All quiet No new patches or notable KBs since Friday
  • Terraform & Packer Nothing new vsphere 2.18.0 is still the newest release
  • Next deadline 4 days VMware Explore on Tour London, 18 Nov

Key Takeaways

  • Urgent If vCenter still isn't patched for CVE-2026-59310, make it today's job, and keep the Brotli workaround in place on SDDC Manager. CVE-2026-59310 has been in CISA's Known Exploited Vulnerabilities catalogue since 18 August; the VMSA-2026-0006 matrix lists vCenter 9.1.0.0300, 9.0.2.0100 and 8.0 U3k as fixed. VMSA-2026-0008.1 still shows "Patch pending" for every SDDC Manager version, so KB 460732 on 9.1.1 (or KB 460734 on 5.2.x, 9.0.2 and 9.1.0) is still your protection.
  • Before upgrading Before your next vCenter upgrade in VCF 9.1, reserve a temporary IP address on the management subnet and check the portgroup security settings. The VCF 9.1 upgrade prerequisites ask for a temporary IP for each vCenter appliance upgrade, and KB 313288 warns that MAC Changes or Forged Transmits set to "Reject" on the vCenter's portgroup could prevent a successful Reduced Downtime Upgrade. Both are quick to check now and painful to discover mid-window.
  • Before upgrading Rewrite storage_policies as storage_policy blocks before you move to vsphere provider 2.18.0. The 2.18.0 release replaces the attribute on vsphere_namespace and its data source, so keep ~> 2.17 pinned until your namespace code is updated.
  • This month Check which of your ESX hosts accept SSH, from where, and who is on their lockdown exception lists. In the Check Point report the attackers reached ESXi over SSH as vpxuser. The vSphere 9.0 docs say that with lockdown mode on, SSH and the ESXi Shell are open only to DCUI.Access users and Exception Users with administrator privileges, so a host in lockdown with SSH stopped closes that particular door.
  • Watch Broadcom still hasn't said whether VCF, NSX or ESX is affected by the Linux kernel TCP flaw CVE-2026-98432. So far there are statements only for Tanzu and Bitnami images (KB 461242, Tanzu fix still pending Canonical) and for vDefend (KB 461249, not affected).

Security Advisories Latest four

There's no new VMSA this weekend, so these are the four most recently released or updated advisories; Broadcom's advisory portal has the rest. If vCenter isn't yet patched for CVE-2026-59310 in VMSA-2026-0006, that's still the priority, and VMSA-2026-0008.1 still lists "Patch pending" for every SDDC Manager version. On the wider industry front, Broadcom's KB 459989 still says there are "zero affected products in the VMware Cloud Foundation product line" for PHP2Shell. There's still no Broadcom statement on the OpenSSH "SSHole" flaw CVE-2026-123158, and for the Linux kernel TCP flaw CVE-2026-98432 the only statements remain KB 461242 for Tanzu and Bitnami images and KB 461249 for vDefend.

VMSA-2026-0008.1 Critical Open Rev .1 · 28 Oct 2026

Node.js, as used in SDDC Manager, has a Brotli decoder out-of-bounds write that an attacker with network access to SDDC Manager could use to run code. It is critical (9.8) on SDDC Manager 9.1.1.x and important (7.5) on 9.0.x, 9.1.0 and 5.2.x; revision .1 on 28 Oct clarified the impacted products in the response matrix. Every fixed version is still "Patch pending", and SDDC Manager 9.1.1.0200 is still the newest 9.1.1 patch on TechDocs. Broadcom's portfolio statement KB 460791 says that, apart from SDDC Manager in VCF 9.1.1, none of its products are critically affected. Press reports say CISA added the underlying Brotli flaw to its KEV catalogue on 27 Oct; the Broadcom advisory itself makes no statement on exploitation. Issue date 27 Oct 2026.

  • CVE-2026-111497 9.8 SDDC Manager Node.js Brotli · 9.8 on 9.1.1, 7.5 elsewhere · reported KEV 27 Oct

DoApply KB 460732 on 9.1.1 or KB 460734 on 5.2.x, 9.0.2 and 9.1.0, keep SDDC Manager reachable only from trusted admin hosts, and subscribe to the advisory so you see the patch the day it lands.

VMSA-2026-0007 Critical Open Initial · 3 Sep 2026

For desktop hypervisors: Workstation and Fusion 25H2 and 26H1, CVSSv3 8.1 to 9.3. Both CVEs need local admin rights inside a guest and can lead to code execution on the host. There are no workarounds and the advisory makes no statement on exploitation.

  • CVE-2026-59346 9.3 VMXNET3 integer overflow
  • CVE-2026-59347 8.1 HGFS stack overflow

DoUpdate Workstation and Fusion to 26H1u1, especially if you run nested labs on a laptop.

VMSA-2026-0006.2 Critical Exploited Open Rev .2 · 19 Aug 2026

Still the one to prioritise. It covers vCenter, ESX, Workstation and Fusion (and so VCF, VVF and Telco Cloud), CVSSv3 2.7 to 9.8, with no workarounds. CISA added vCenter CVE-2026-59310 to its KEV catalogue on 18 Aug 2026 with known ransomware use. SecurityWeek [Press] has reported that CISA added the ESX logging flaw CVE-2026-41709 on 28 Oct. The Broadcom advisory itself makes no statement on exploitation. First published 29 Jul 2026; revision .2 on 19 Aug added 7.0 guidance for the critical issues.

  • CVE-2026-59309 9.8 vCenter VMDir auth bypass
  • CVE-2026-59310 9.8 vCenter Syslog traversal · KEV
  • CVE-2026-47876 9.3 ESX VMXNET3
  • CVE-2026-41703 7.6 ESX OOB read
  • CVE-2026-41709 2.7 ESX logging · reported KEV 28 Oct

DoPatch vCenter to 9.1.0.0300, 9.0.2.0100 or 8.0 U3k (8.0 U2f is also listed; VCF 5.x: async patch to 8.0 U3k per KB 88287). On ESX 9.0, ESXi-9.0.2.0100-25595025 covers all three ESX CVEs. On 9.1 the matrix lists ESXi-9.1.0.0200-25557999 for CVE-2026-47876 and ESXi-9.1.0.0-25370933 for the other two. On 8.0, ESXi80U3k-25595708 fixes CVE-2026-47876, U3i-25205845 CVE-2026-41703 and U3j-25429389 CVE-2026-41709. vCenter 7.0 fixes need an extended support contract.

VMSA-2026-0005.1 Critical Open Rev .1 · 7 Aug 2026

If you run Avi Load Balancer (including for VKS or VCF Automation), this one matters. Seven CVEs, CVSSv3 7.1 to 9.8, no workarounds; the worst, CVE-2026-47865, is an authentication bypass. The advisory makes no statement on exploitation. First published 14 Jul 2026; revision .1 on 7 Aug added the 22.1.7-2p12 patch.

  • CVE-2026-47865 9.8 auth bypass
  • CVE-2026-47871 8.8 directory traversal
  • CVE-2026-47867 8.7 RCE
  • CVE-2026-47869 8.7 authenticated RCE
  • CVE-2026-47866 8.3 authorisation bypass
  • CVE-2026-47868 7.8 local privilege escalation
  • CVE-2026-47870 7.1 privilege escalation

DoUpgrade 32.1.1 to 32.1.2 or later (the advisory's recommended version), 31.1.1–31.2.2 to 31.2.2-2p3, and 30.1.1–30.2.6 to 30.2.7. On 22.1.x, 22.1.7-2p12 fixes CVE-2026-47865, but the matrix lists 30.2.7 for the other six.

All VMware security advisories on Broadcom's support portal →

KB Articles & Known Issues Nothing new

No new VMware KBs of note since Friday, and nothing has moved on the articles we follow. KB 457944 still points to vCenter 9.1.1.0100 (build 25784172) for the missing Supervisor Control Plane VMs. KB 458671 (NSX Manager startup with host-based agent VM services) still has only the proton timeout workaround, KB 452660 (SCRX after an NSX 9.0.1 to 9.1.1 upgrade) is still "resolved in the upcoming NSX version", KB 456305 still has a fix planned for the Identity Broker certificate alerts, and KB 460199 on the eMudhra certificates still names no fixed versions.

Releases & Release Notes Nothing new

No new VCF patches since 26 October. The 9.1.1.x patch index still tops out at SDDC Manager 9.1.1.0200, vCenter, ESX and NSX 9.1.1.0100 and vSAN File Services 9.1.1.0200, and the VCF 9.1 release notes list no line beyond 9.1.1. VMware Tools 13.1.6, Avi Load Balancer 32.1.4 and VKS 3.8 are unchanged.

Automation & IaC

Terraform & Packer Nothing new

Nothing new from the providers or Packer plugins this weekend. The vsphere provider 2.18.0 from 9 November is still the latest, with its storage_policy breaking change on vsphere_namespace, and vcf 0.19.0 is still the one to use for VCF 9.1.1, per the README.

Automation & API Ecosystem Nothing new

All quiet on the wider toolchain too: VCF.PowerCLI 9.1.1 is still the current gallery version, and govmomi 0.56.2, vmware.vmware 2.13.0 and vmware.vmware_rest 5.1.0 are unchanged.

Deep Dive of the Day

Reduced Downtime Upgrade for vCenter: how it works, and what VCF 9.1 asks of you

Sooner or later every VCF estate has a vCenter upgrade that isn't a quick patch: 9.0 to 9.1, or the 8.x to 9.x move that the 11 October 2027 end of service for vSphere 8 makes unavoidable. Broadcom's own guidance draws the line clearly. Broadcom's post on rapid vCenter patching in VCF 9.1 recommends Quick Patch for compatible maintenance patches, where vCenter changes "only those specific RPMs or binaries that have a code change", and Reduced Downtime Upgrade (RDU) for minor updates and major upgrades such as 9.0.0 to 9.1.0. It also points out that using RDU for a patch Quick Patch could handle "would increase the overall maintenance time", so pick the right tool for each job.

RDU is a migration rather than an in-place upgrade. As the vSphere 8 Update 3 RDU post explains, a new vCenter appliance is deployed, the current vCenter's data and configuration are copied across while it stays online, and then a switchover moves services to the new appliance. That switchover is the only outage, which the post says "typically takes less than 5 minutes"; Broadcom's older KB 313288, written for 8.0 Update 2, puts it at about 10 minutes. Since 8.0 Update 3 you can let the switchover run automatically or start it yourself, which is useful when you want the copy done in the afternoon and the cut-over in your change window.

The same 8.0 Update 3 post lists the topologies RDU handles: self-managed vCenters, vCenters managed by another vCenter (7.0 or later), Enhanced Linked Mode and vCenter HA. Two cautions come with that. In Enhanced Linked Mode, "Do not update multiple vCenter instances in parallel", so upgrade linked vCenters one at a time. With vCenter HA, RDU removes HA before the upgrade and reactivates it afterwards, but only orchestrates that for HA instances on 8.0 Update 2 or later; on anything older you deactivate and reactivate HA yourself.

VCF 9.1 adds a couple of conveniences. The What's new in vSphere for VCF 9.1 page says you can now "run on-demand pre-checks for RDU", like the regular patching pre-checks, and "download payloads automatically by using RDU as opposed to downloading an ISO image". It also notes that the vCenter VM hardware version moves from vmx-10 to vmx-17 with 9.1, worth knowing if anything in your tooling keys off the VM's hardware version. On the VCF side, the upgrade prerequisites ask you to "Allocate a temporary IP address for each vCenter appliance upgrade" from the management subnet (it can be reused), to take file-based or image-based backups of SDDC Manager and every vCenter and NSX Manager, and to take a cold snapshot of SDDC Manager.

The gotchas worth knowing come mostly from KB 313288. The target must be the same size as the source or larger. On the vCenter's portgroup, MAC Changes and Forged Transmits must not be set to "Reject", because that "could prevent from a successful upgrade". Don't run an RDU and a VAMI update at the same time, which "may lead to a corrupt vCenter Server", and keep it to one administrator at a time. If the upgrade fails, it reverts to the source automatically. If it succeeds, disconnect the old appliance's network adapter: the KB warns that powering the source back on cancels the upgrade and deletes the target. The KB is written for 8.0, so treat these as the mechanics 9.x inherits and check the 9.1 docs for anything newer.

For nested labs, budget datastore space and an address for a second vCenter appliance while both run side by side, and remember the portgroup setting above if your nested management network sits on a portgroup you've locked down. Andy's World found RDU cut downtime from over an hour with VAMI to about 10 minutes on 8.0.3, with one surprise: the ISO-based flow needed the original 8.0.3 ISO to hand. In 9.1 the automatic payload download should spare you that, but it's a good habit to keep the current ISO in your content library anyway.

Based on vCenter Server upgrades with the reduced downtime (KB 313288) Official vCenter Reduced Downtime Update in VMware vSphere 8 Update 3 (VCF Blog) Official What's new in vSphere, VCF 9.1 release notes Official Rapid Patching of VMware vCenter in VMware Cloud Foundation 9.1 (VCF Blog) Official Prerequisites for Upgrading the VCF Core Components Official Updating vCenter 8.0.3 to 8.0.3a with RDU (Andy's World) Community

Community & Learning

Videos, Podcasts & Events Latest episodes

Certification & Learning Nothing new

No exam changes this week. The VMware vSphere Foundation 9.0 Administrator exam (2V0-16.25) has a November 2026 exam guide, and the three role-based VCF 9 VCAP exams, Administrator (3V0-11.26), Architect (3V0-12.26) and Support (3V0-13.26), are unchanged.

Sources (24)

Recent Briefings

Full archive → RSS

Tags: Official Broadcom and VMware sources, Press trade press, Community community posts and unverified reports.

Thanks for visiting

Let's talk tech!

Questions, ideas, or just want to talk VCF? Drop me an email or find me on the socials.

Email me →