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

It's a gentle start to the week: no new VCF patches, KBs or provider releases since Friday. The one thing worth keeping an eye on is Apache's critical 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 now public, but Broadcom hasn't yet said whether any VMware product is affected. If your scanners start flagging appliances, that's the KB you'll want to see.

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

Elsewhere, VMware Explore on Tour London is on Wednesday and Broadcom reports its fiscal year results on 9 December. Today's deep dive looks at stretching vSAN clusters across two availability zones in VCF 9.1: the order you have to do things in, the witness, and the restrictions that catch people out.

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 2 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 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 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. Yesterday's deep dive on VCF Single Sign-On covers how to put MFA in front of vCenter and NSX logins.
  • Lab If you rehearse a stretched cluster in your lab, stretch the management domain first and keep the witness on the same ESX build as the hosts. The VCF 9.1 stretching guide requires the management domain cluster to be stretched before any workload cluster, and the witness page says the witness must match the hosts' ESX version, using the ESA appliance for ESA and vSAN storage clusters. Today's deep dive has the rest.
  • 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 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 and says nothing about HTTP/2. 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 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, and the PHP2Shell, Brotli and Linux TCP statements (KB 459989, KB 460791, KB 461242 and KB 461249) 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 since the weekend. The 9.1.1.x patch index was last touched on 12 November but 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 (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.

Deep Dive of the Day

Stretching vSAN clusters across two availability zones in VCF 9.1

If you're building VCF for two sites, a stretched vSAN cluster is how you get the planned-maintenance and disaster-avoidance story without a separate recovery product. The VCF 9.1 stretching guide describes splitting a workload-domain cluster across two availability zones in one region, with both zones holding an equal number of hosts so either can carry the load if the other goes down. It works for vSAN ESA and OSA clusters, and for vSAN compute and vSAN storage clusters (formerly vSAN Max), and the guide documents stretching and unstretching as SDDC Manager API procedures rather than UI workflows: POST /v1/clusters to create a stretched compute cluster, and PATCH /v1/clusters/{id} to stretch an existing one.

Order matters. The default management domain cluster has to be stretched before any workload-domain cluster, so that vCenter, the NSX management cluster and SDDC Manager stay reachable if the primary zone fails. A vSAN storage cluster also has to be stretched before any of the compute clusters that mount it. One 9.1 detail that surprises people: VM-Host affinity rules you create for zone placement don't apply to the VCF management services VMs. Those use Cluster API Provider vSphere node anti-affinity instead, and the guide says DRS rules are neither required nor honoured for them.

The witness is the piece most often got wrong. vSAN HCI and vSAN storage stretched clusters need a witness in a third location that is neither availability zone; vSAN compute clusters don't need one. The witness page says it must run the same ESX version as the hosts in the stretched cluster, that you deploy the ESA appliance for vSAN ESA and vSAN storage clusters and the OSA appliance for OSA, and that you register it with vCenter, set NTP and configure its VMkernel adapters for the witness network. That version rule is why the witness builds (25784021 for ESA and 25783993 for OSA) appear alongside each ESX patch in the 9.1.1 patch index: patch the witness with the hosts.

There are hard stops worth checking before you start. You can't stretch a cluster that shares a vSAN storage policy with another cluster, that contains DPU-backed hosts, whose hosts within one zone sit in different L3 subnets, or that is a vSAN ESA or vSAN Max cluster with Global Deduplication turned on. Undoing it is also an API job: unstretching needs every snapshot on the cluster consolidated or deleted first (and, for a vSAN storage cluster, any stretched compute clusters using it unmounted), removes all the second zone's hosts and leaves a standard vSAN cluster, and for compute-only clusters stretched from 9.1 onwards you have to name the zone to remove with azToRemove.

The TechDocs pages don't give numbers for the links, so it helps to have a design reference to hand. Pranay Jha's VCF 9.1 walkthrough works to 5 ms round trip and at least 10 Gbps between data sites, up to 200 ms and 100 Mbps to the witness, at least three hosts per zone, and a separate network pool for the second zone so its vSAN and vMotion ranges don't overlap. It also flags two traps: if you stretch a VLAN you must stretch its gateway too, or return traffic breaks after a failover, and its sample API payloads use a slightly different shape for the validation call and the PATCH, so check the schema in the SDDC Manager API reference before running either. Treat those figures as that author's design guidance and confirm them against Broadcom's vSAN stretched cluster guidance for your build.

In a nested lab you can rehearse the whole flow cheaply: two small groups of nested hosts, a witness appliance on a third network and the API calls from the SDDC Manager API Explorer in VCF Operations. The write-up suggests measuring latency with vmkping before you commission anything, matching the witness build to the hosts so validation doesn't reject it, and finishing with a real test, putting one zone into maintenance mode and checking that vSphere HA restarts the VMs on the other side.

Based on Stretching vSAN Clusters in VMware Cloud Foundation (TechDocs 9.1) Official Deploy and Configure vSAN Witness Host (TechDocs 9.1) Official Unstretch a Cluster in VMware Cloud Foundation (TechDocs 9.1) Official How to Configure a Stretched Cluster in VCF 9.1 (Pranay Jha) Community

Industry Three to note

Licensing, Business & Industry News Three to note

  • Apache Patches Critical HTTP Server RCE Found by Anthropic, Google SecurityWeek 12 Nov Press The one industry vulnerability to have on your radar this week. CVE-2026-119618 is a race condition in mod_http2 that can corrupt memory and, per Red Hat's 9.8 score, allow unauthenticated code execution. It affects Apache HTTP Server 2.4.55 to 2.4.70 with HTTP/2 enabled and is fixed in 2.4.71, released on 11 November. If you can't update yet, turning HTTP/2 off is the stop-gap. Broadcom hasn't said whether any VMware product is affected.
  • CVE-2026-119618: Apache mod_http2 Remote Code Execution Horizon3.ai 12 Nov Press A useful status page: a third-party proof of concept published on 12 November reproduces the heap corruption on 2.4.70 but doesn't show code execution, and no exploitation in the wild had been confirmed when it was written. Worth bookmarking so you know where things stand if your scanners light up.
  • Broadcom Inc. to Announce Fourth Quarter and Fiscal Year 2026 Financial Results on Wednesday, December 9, 2026 Broadcom Investor Relations 9 Nov Official Broadcom reports its fourth-quarter and full-year results after US markets close on 9 December, with the call at 2pm Pacific. It's usually where the latest VMware customer and VCF adoption numbers get aired, so it's worth a skim if licensing conversations are on your plate.

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 (30)

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 →