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

The security world is busy with Java4Shell (CVE-2026-114938), a memory-corruption bug in Java's fast Base64 decoder that Oracle patched yesterday and that researchers say can lead to code execution in apps like Jenkins, Jira and Keycloak. Broadcom hasn't said yet whether any VMware product is affected, so patch the Java services you run yourself, such as your CI and artefact servers, and leave the VMware appliances alone until there's a KB.

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

If you're upgrading to VCF 9.1, two new things deserve your attention: a KB on host licences that stop renewing when ESX is patched before VCF Operations, and William Lam's guide to upgrade order when several vCenters share one NSX Manager. The VCF blog also makes the case for VPC networking under VKS. Today's deep dive explains vSAN storage clusters and compute clusters in VCF 9.1, and what changed from 9.0.

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 Three KBs worth reading No new VCF patches today
  • Terraform & Packer Nothing new vsphere 2.18.0 is still the newest release
  • Next deadline Today 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.x and 9.1.0) is still your protection.
  • Before upgrading Patch VCF Operations and the License Server to 9.1.1 before you patch any ESX host to 9.1.1. KB 456235 says hosts patched first reject their host-scoped licences with "License assignment failed for this host" and a generation-number error in hostd.log, and their licences eventually expire. There's no fix version yet; the workarounds are a fresh License Server with migrated entitlements, or assigning a different valid licence to the host.
  • Before upgrading If several vCenters share one NSX Manager, plan when you'll run the NSX Upgrade Finalizer. In William Lam's walkthrough the Finalizer only runs once every connected vCenter and ESX host is on 9.1.x, and NSX 9.1 features stay off until then, although the vSphere upgrades themselves don't depend on it. If an imported workload domain is due to be retired, you can leave it unfinalised and still get fleet management.
  • This month Patch the Java services you run yourself for Java4Shell, and wait for Broadcom before touching VMware appliances. Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, per Tenable; standard Java 8 and 11 aren't affected, and only x86-64 CPUs with AVX-512 VBMI are. -XX:-UseBASE64Intrinsics is the stop-gap researchers suggest for your own JVMs. Broadcom has published nothing yet, and its appliance policy KB is the reason not to change JVM flags on vCenter or SDDC Manager by hand.
  • Lab If you try the VPC network stack for VKS in your lab, check the MTU on your VMkernel interfaces first. The VCF blog says full-stack VPC needs an MTU of at least 1700 on the vmkernel interfaces, though it can start on a single VLAN with no BGP or Edge cluster. It also says the vSphere Distributed Switch stack still suits labs and smaller deployments.

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 yet published a statement on Java4Shell (CVE-2026-114938), the OpenJDK Base64 flaw Oracle patched on 17 November; its existing KB 434436 on OpenJDK findings in vCenter 8.x doesn't mention it. There's also still no statement on the Apache HTTP/2 flaw CVE-2026-119618 (KB 443715 covers only earlier Apache CVEs on vCenter 8.x), or on OpenSSH "SSHole" CVE-2026-123158. KB 459989 still says there are "zero affected products in the VMware Cloud Foundation product line" for PHP2Shell, and for the Linux 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.x 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 Three worth reading

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 460791 still says only SDDC Manager in VCF 9.1.1 is critically affected by the Brotli flaw, and the eMudhra article, KB 460199, still names no fixed versions. KB 458671 (NSX Manager startup), KB 452660 (SCRX after an NSX upgrade) and KB 456305 (Identity Broker certificate alerts) are still waiting on fixes.

  • KB 456235: ESXi 9.1.1 hosts fail to accept host-scoped licences after VCF Operations or the License Server is upgraded Broadcom KB Undated Official This one is about upgrade order. If hosts reach ESX 9.1.1 before VCF Operations or the License Server does, they show "License assignment failed for this host", raise HostRejectedLicenseEvent alarms and stop getting licence updates, so the licences eventually expire. Workloads aren't affected. No fix version yet; workarounds are deploying a fresh License Server and migrating entitlements, or assigning a different valid licence to the host, and vim-cmd vimsvc/license --show shows where a host stands.
  • KB 458395: VCF management component upgrade prechecks fail on a VMSP version mismatch Broadcom KB Undated Official Upgrading Identity Broker, Log Management or Salt Master in 9.1.x can fail with VCFMS-PRECHECK-VIDB-VMSP-VERSION-001, claiming VCF services runtime is still on 9.1.0 when it isn't. The cause is stale lifecycle metadata; the fix is the Sync button next to "Last lifecycle metadata sync time" under Build, Lifecycle, VCF Management in VCF Operations, then retry. Worth checking that timestamp before you start.
  • KB 461167: false "VCF Operations password has expired" alerts in 9.1.1 Broadcom KB Undated Official If VCF Operations 9.1.1 keeps telling you a password has expired, or will in 30 days, on the https://localhost/suite-api object while Fleet Management shows nothing expired, it's two duplicate alert definitions reading a stale metric. Broadcom is working on a fix; meanwhile you can deactivate both definitions in the policy for the Operations App object type.

Releases & Release Notes Nothing new

No new VCF patches today. The 9.1.1.x patch index and the vCenter, ESX, NSX and SDDC Manager patch notes all show a 16 November page update but no new 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). 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 the newest 32.1 release, VKS 3.8.0 is current and VMware Tools 13.1.6.0 is unchanged.

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. If your pipelines run on Jenkins, Artifactory or Keycloak, those are among the apps researchers name for Java4Shell, so check their JDKs today.

Nested Lab Corner Nothing new

Nothing new for nested labs since Holodeck 9.1.1 on Monday. If you rehearse shared-NSX upgrades in a lab, William Lam's post below is a good script to follow, and the VKS VPC post has the MTU figure your nested VMkernel interfaces need.

Deep Dive of the Day

vSAN storage clusters and compute clusters in VCF 9.1: what changed since 9.0, and the choice you make at creation

Most VCF domains start life as vSAN HCI clusters, where every host gives both compute and storage. The VCF 9.1 storage models page adds a disaggregated pair: a vSAN storage cluster that only serves storage (what used to be called vSAN Max, as Pranay Jha notes), and a vSAN compute cluster that has no local vSAN storage and mounts a datastore from the storage cluster instead. The point is to let compute and storage grow on their own timelines, so a CPU-hungry workload domain doesn't force you to buy capacity drives, and vice versa.

There are firm rules about where they can go. Storage clusters need vSAN ESA, so NVMe drives only, and Broadcom doesn't recommend running VMs on them. Neither type can be the management domain's default cluster; both are supported for additional management clusters and workload domains. A compute cluster must sit in the same workload domain as its storage cluster, and a single-rack compute cluster can be stretched across two availability zones while a multi-rack compute cluster supports a single zone only.

VCF 9.1 relaxed some limits from 9.0. The 9.0 sharing rules say OSA and ESA can't share datastores, a storage cluster can't be mounted by an OSA client, and data-in-transit encryption between client and server clusters isn't supported. The 9.1 what's new page says compute-only clusters can now mount OSA and storage-cluster datastores at the same time, stretched storage clusters can serve storage across vCenter boundaries, and disaggregated vSAN gains in-transit encryption between client and storage clusters. If you read a 9.0-era design guide, check it against 9.1 before you rule anything out.

Some numbers don't change. Per the sharing rules, a datastore can be shared with up to 10 client clusters, a client cluster can mount up to 5 remote datastores, and no more than 128 hosts in total can mount one datastore. A storage cluster needs at least 4 hosts, and Broadcom recommends 6 or more; its design guidance says 7 or more lets the cluster get its resilience back after a sustained host failure and supports RAID-6. Client-to-server latency must stay under 5 ms. On bandwidth, 25 GbE between storage hosts is supported and 100 GbE recommended (smaller storage clusters may use 10 GbE), while clients can connect at 10 GbE with 25 GbE recommended.

The decision you can't undo is the cluster type. The sharing rules say it's set when the cluster is created, and turning an HCI cluster into a storage cluster means turning vSAN off and reconfiguring it. Two other traps: set vSphere HA's APD response on client clusters to power off and restart VMs, and remember that storage policies are per vCenter, so when client and storage clusters sit under different vCenters it's the policy on the client cluster's vCenter that applies. Pranay Jha's design notes add a sensible sizing habit: plan on usable capacity, not raw, and start with four devices per host rather than the two-device minimum, so a drive failure leaves room to rebuild locally.

For a nested lab, a small storage cluster plus a compute cluster is a good way to learn the mount, policy and failure behaviour without much hardware. Just remember that a 4-host minimum, ESA and NVMe-only devices still apply, so nested NVMe controllers and the usual HCL workarounds come into play, and that what you see in a lab says nothing about performance.

Industry

Features & Technical Blogs Three worth reading

  • VCF 9.1.x Upgrade Sequence with Shared NSX Manager williamlam.com 17 Nov Community If several vSphere environments share one NSX Manager, this lays out two orders. In both you converge the first vCenter as the management domain, upgrade NSX 4.2.x and vCenter 8.0 U3 to 9.1.x there, then import the other vCenters as workload domains. Upgrading those and running the NSX Upgrade Finalizer completes the job and turns on NSX 9.1 features; skipping the Finalizer lets you defer the imported domains, which suits ones due for retirement.
  • Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack VCF Blog 17 Nov Official Broadcom calls VCF Networking with VPC the recommended, default Supervisor stack in 9.1. Nodes sit on private subnets, load balancing runs on an active/active Virtual Network Appliance cluster of up to ten nodes rather than one active/standby Foundation Load Balancer pair, and you can start on a single VLAN without BGP or an Edge cluster. It needs vmkernel MTU of at least 1700, and as of 9.1.1 a VLAN-backed VPC can't create private networks.
  • The GitOps Advantage: How VCF Automation Reduces Ephemeral Environment Toil by Up to 80% VCF Blog 17 Nov Official A Broadcom-commissioned Principled Technologies test of VCF Automation with VKS Cluster Management, Argo CD and Velero: hands-on admin time for ephemeral dev environments fell by up to 79.8% and environment lifecycle time from 21m20s to 4m18s. Treat it as a vendor-commissioned result, but the pattern of one Git commit per environment is a useful one if you run VKS for developers.

Licensing, Business & Industry News All quiet

Nothing new on the business side since yesterday. Broadcom reports its fourth-quarter and fiscal 2026 results on Wednesday 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 three role-based VCF 9 VCAP exams, Administrator (3V0-11.26), Architect (3V0-12.26) and Support (3V0-13.26), are unchanged.

Sources (41)

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 →