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

Weekday edition · archive

If you rehearse VCF in a nested lab, Broadcom released Holodeck 9.1.1 yesterday. It adds VVF and VCF 9.1.1 support, lets you deploy VCF 9.1 patch releases greenfield without waiting for a new Holodeck build, and checks depot connectivity and your ovftool, ISO and OVA files before the VCF Installer runs, which should mean fewer half-built labs.

There's no new VMSA today, and if vCenter CVE-2026-59310 isn't patched yet it's still the one to do first.

Elsewhere, the VCF blog walks through building a VCF 9.1 Installer depot by hand when you can't get a download token, and shows how to alert on new VCF services runtime nodes in VCF Operations. VMware Explore on Tour London starts tomorrow. Today's deep dive covers commissioning hosts and network pools in VCF 9.1, including the one subnet decision you can't take back.

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 VCF patches or notable KBs
  • Terraform & Packer Nothing new vsphere 2.18.0 is still the newest release
  • Next deadline 1 day Explore on Tour London, 18–19 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 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 Treat vCenter as Tier 0: keep its admin identities apart from everyday domain accounts, and alert when a Host Profile turns SSH on. In Kaspersky's write-up of the BlackNevas case the attackers needed no VMware bug, just credentials from elsewhere, root SSH to vCenter and a Host Profile that switched on SSH across the hosts. Kaspersky suggests alerting on Host Profile remediation that changes TSM-SSH outside a change window, forwarding ESX and vCenter logs off-box, and running backups under identities separate from production AD.
  • Lab If your nested VCF lab runs on Holodeck, move to 9.1.1 before you build your next 9.1.1 environment. Holodeck 9.1.1 supports VCF 9.1.1 and VVF, can deploy VCF 9.1 patch releases greenfield, and fixes the VCF Installer being deployed with only one DNS server and an NSX Edge cluster failure in the 9.1 management domain, per the release notes. The physical host needs ESX 8.0 U3 or later.
  • Watch Keep an eye out for a Broadcom statement on the Apache HTTP/2 flaw CVE-2026-119618. Apache fixed it in HTTP Server 2.4.71 on 11 November, and a crash proof of concept is public. Broadcom hasn't said whether any VMware product is affected, so for now patch the Apache servers you own, consider turning HTTP/2 off where you can't, and don't change VMware appliances outside a Broadcom KB.

Security Advisories Latest four

There's no new VMSA today, 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 still hasn't published a statement on the critical Apache HTTP Server HTTP/2 flaw CVE-2026-119618 (fixed upstream in 2.4.71 on 11 November); its existing KB 443715 covers scanner findings for earlier Apache CVEs on the vCenter Server Appliance. 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 (12 Oct) 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 yesterday, 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, and the PHP2Shell and Brotli statements (KB 459989 and KB 460791) read as before. The eMudhra article, KB 460199, still names no fixed versions; Broadcom says it will address the issue "in upcoming product releases and documentation". KB 458671 (NSX Manager startup), KB 452660 (SCRX after an NSX upgrade) and KB 456305 (Identity Broker certificate alerts) are still waiting on fixes.

Releases & Release Notes Nothing new

No new VCF patches today. The 9.1.1.x patch index and the NSX 9.1.1.0100 release notes were both touched on 16 November, but neither adds a release: the newest builds are still SDDC Manager 9.1.1.0200, vCenter, ESX and NSX 9.1.1.0100 (12 October) and vSAN File Services 9.1.1.0200 (26 October), and the release notes index shows no 9.1.2 or 9.2 line yet. Outside the core stack, ESXi 8.0 U3k (build 25595708, 29 July) is still the newest 8.0 patch, Avi 32.1.4 is still the newest 32.1 release, VKS 3.8 heads the VKS release notes and VMware Tools 13.1.6.0 is still current.

Automation & IaC

Terraform & Packer Nothing new

Nothing new from the providers or Packer plugins today. 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. nsxt 3.12.1, vcfa 1.2.3 and avi 32.1.4 are unchanged, as are the vsphere (2.5.1) and vmware (2.1.7) Packer plugins.

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.

Nested Lab Corner Holodeck 9.1.1

  • Announcing the General Availability of Holodeck 9.1.1 VCF Blog 16 Nov Official The nested VCF toolkit gets a patch release that adds VVF and VCF 9.1.1, greenfield deployment of VCF 9.1 patch releases, and custom VM and template folders when you deploy to a vCenter target. It supports VCF 9.0.0 to 9.1.1 and 5.2 to 5.2.4, and the physical host needs ESX 8.0 U3 or later.
  • Holodeck release notes: 9.1.1 patch release vmware/Holodeck on GitHub 16 Nov Official Worth a skim for the fixes alone: the VCF Installer no longer deploys with a single DNS server, an NSX Edge cluster failure in the 9.1 management domain is fixed, and Reset-HoloRouter and Remove-HoloDeckInstance now do what they say. Dual-site labs get their own bgpRouterConfiguration.yaml. The release notes list the release as October 2026; Broadcom announced it on 16 November.
Deep Dive of the Day

Commissioning hosts and network pools in VCF 9.1: the groundwork for every new cluster

Every host you add to VCF, whether for a new workload domain or to grow a cluster, goes through commissioning first. Per the VCF 9.1 docs, commissioning adds ESX hosts to the global inventory, and they then sit in the Unassigned Hosts list until a domain or cluster claims them. In 9.1 you start it from the vSphere Client (Global Inventory Lists, Hosts, Unassigned Hosts, Commission Hosts) on the management domain vCenter, or from a vCenter linked through VCF Single Sign-On; the SDDC Manager UI is still there as an alternative. Christopher Lewis notes that it isn't in VCF Operations, which catches people who expect everything there now.

The checklist is where most failures start. Hosts need forward and reverse DNS with the host name matching the FQDN, a self-signed certificate regenerated for that FQDN, a management VMkernel interface on a standard switch with a gateway in the management subnet, hardware on the compatibility guide, and every old disk partition removed. If your environment uses CA-signed host certificates, new hosts must use them too. Commissioning briefly turns on SSH to read the host key and turns it off again, and it creates test VMkernel adapters to check vMotion, so MAC address filtering on the physical network can make that check fail.

You choose a storage type per host, and that choice sticks. The bulk JSON import accepts VSAN, VSAN_ESA, VSAN_REMOTE (vSAN compute), VSAN_MAX (vSAN storage), NFS, VMFS_FC and VVOL, and the docs say a commissioned host can only be used with clusters of the same storage type: vSAN ESA hosts for ESA clusters, OSA hosts for OSA clusters, and so on. Getting it right at commissioning saves you a decommission later. Validation runs against every host, the wizard asks you to confirm each fingerprint, and by default failed hosts are skipped so the rest carry on.

Every host also needs a network pool, which must exist first and match the storage type. A pool holds the VLAN, MTU, subnet and IP ranges for the vMotion and storage VMkernel ports, so you only give an address for vmk0 and VCF hands out the rest. vSAN needs vMotion and vSAN networks, vSAN storage clusters add a vSAN Storage Client network, and NFS needs vMotion and NFS. The management domain gets a default pool at deployment, which can't be deleted, and you need a new pool for hosts on a different Layer 2 network.

The decision you can't undo is the subnet. The docs say a pool's subnet cannot be changed after it's deployed; you can add IP ranges to grow into it, and the sizing guidance recommends starting with a larger subnet than you need today. A pool can only be deleted once no host with an address from it belongs to a workload domain, and you can't mix IPv4 and IPv6 for the same traffic type within a cluster. Size vMotion and vSAN subnets for the hosts you expect in three years, not the four you're commissioning this week.

In a nested lab the same rules apply, with a couple of extra hurdles. Nested hosts usually fail the 10GbE NIC speed and vSAN ESA disk compatibility checks, and Christopher Lewis describes the usual lab-only workaround: adding enable.speed.of.physical.nics.validation=false and vsan.esa.sddc.managed.disk.claim=true to the operationsmanager application.properties on SDDC Manager and restarting the service. That's for labs only. Broadcom's own route for proof-of-concept hardware is KB 408300, which the docs cite for using non-certified ESA disks from VCF 9.0.1.

Based on Commission ESX Hosts (VCF 9.1) Official Network Pool Management (VCF 9.1) Official VCF 9 Day 2: Commissioning new ESX Hosts (thecloudxpert.net) Community

Industry

Features & Technical Blogs Two worth reading

  • Building a VCF 9.1 Installer Depot Offline, without a Download Token VCF Blog 16 Nov Official Syed Qamar shows how to hand-build an offline depot for VCF Installer 9.1.1.0200 (about 65 GB) when the VCF Download Tool can't get an activation code, then upload it with VCFDT's binaries upload command. The gotchas are useful for any air-gapped build: a single missing yaml or plugin file makes the installer silently skip a bundle, folder names are case-sensitive, and the vcf_lcm user must be able to read every file. Entitled customers should still use the token-based VCFDT procedure.
  • Know the Moment Your VCF Platform Changes: Alerting on New Services Runtime Nodes VCF Blog 16 Nov Official In VCF 9.1.x the management services run on VCF services runtime, whose worker nodes are ordinary VMs that appear during scale-outs, upgrades and node recovery. Brian O'Connell builds a VCF Operations alert that spots a new node by matching its hardware UUID to the runtime's node object, then uses it to send email, drop the VM into a DRS group through an orchestrator workflow, or update a CMDB. Handy if your change process expects to know about every new VM in the management domain.

Licensing, Business & Industry News All quiet

Nothing new on the business side since yesterday. Broadcom reports its fourth-quarter and fiscal 2026 results on 9 December, per Broadcom Investor Relations, and that's usually where the latest VCF customer numbers come out.

Community & Learning

Videos, Podcasts & Events New this week

Certification & Learning Nothing new

No exam changes since yesterday. 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 (34)

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 →