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 you haven't yet patched vCenter 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, there's still no Broadcom statement on the OpenSSH "SSHole" flaw CVE-2026-123158, whose federal deadline is today. For the Linux kernel TCP flaw CVE-2026-98432, Broadcom's new KB 461249 says vDefend 4.2.x and 9.x, the vDefend Security Services Platform and License Hub are not affected, adding to KB 461242 for Tanzu and Bitnami images; neither mentions VCF, NSX, vSphere or ESX.
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 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 in the matrix is still "Patch pending", and the only SDDC Manager 9.1.1 patch on TechDocs, 9.1.1.0200, doesn't mention it. Broadcom's portfolio statement KB 460791 says SDDC Manager in VCF 9.1.1 is the only critically affected product. Press reports say CISA added the underlying Brotli flaw to its KEV catalogue on 27 Oct with a federal deadline of 10 Nov, which has passed; 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.
For desktop hypervisors: Workstation 25H2 and 26H1 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.
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] reports CISA added the ESX logging flaw CVE-2026-41709 on 28 Oct, with CrowdStrike linking its zero-day use to the China-nexus group Warp Panda; its federal deadline of 11 Nov has now passed. 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 / U2f (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; ESXi80U2f-25626445 covers only CVE-2026-47876. For VCF 5.x the matrix lists 5.2.4 for CVE-2026-41709.
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 on the Avi control plane. 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 control-plane 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 One KB worth reading
One new statement today, and the articles we follow haven't moved. KB 460791 still names SDDC Manager in VCF 9.1.1 as the only critically affected product for the Brotli flaw, and KB 460199 on the eMudhra certificates still promises fixes in "upcoming product releases" without naming any. KB 458671 (NSX Manager startup with agent VM services) and KB 452660 (SCRX after an NSX 9.0.1 to 9.1.1 upgrade) are still waiting for a fixed NSX version, KB 456305 still has a fix planned for the Identity Broker certificate alerts, and KB 459989 still says no VCF products are affected by PHP2Shell. If you've hit the missing Supervisor Control Plane VMs, KB 457944 confirms the fix is in vCenter 9.1.1.0100.
- KB 461249: vDefend: Impact Assessment of CVE-2026-98432 - Linux Kernel TCP Broadcom KB Official If you run vDefend, this is reassuring: Broadcom says vDefend 4.2.x and 9.x (Distributed Firewall, Gateway Firewall and IDPS), the vDefend Security Services Platform 5.0.x to 5.2.x and License Hub for vDefend and Avi are not affected by the kernel TCP use-after-free, because "existing kernel hardening protections mitigate any potential for exploitation". It doesn't cover NSX, ESX or VCF as a whole, so there's still no platform-wide statement.
Releases & Release Notes Nothing new
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.
Automation & API Ecosystem Nothing new
Another quiet day for the wider toolchain: 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 vSphere Configuration Profiles in VCF 9: keeping host settings where you put them
Yesterday's Broadcom blog lists vSphere Configuration Profiles among the features that keep hardening settings in place across updates and reboots, and after Wednesday's look at execInstalledOnly it's the natural next question: how do you stop host configuration drifting at all? Configuration Profiles let you "manage the configuration of all hosts in a cluster collectively", per the vSphere 9.0 docs. You describe the desired state once as a JSON document backed by a JSON schema, check each host's compliance against it, and remediate the hosts that don't match.
The requirements are modest but the switch is permanent. You need vCenter 9.0 or later; image-managed clusters need ESX 8.0 Update 1 or later on every host, and baseline-managed clusters need 8.0 Update 3 or later, including the reference host. Moving a cluster from Host Profiles "is permanent", and the docs state plainly that "You cannot deactivate vSphere Configuration Profiles." Broadcom's comparison post lists Host Profiles as deprecated in VCF 9 and Configuration Profiles as the strategic mechanism, so this is a one-way door you'll walk through eventually; the point is to walk through it deliberately.
The day-to-day model is different from Host Profiles in useful ways. According to the comparison post, you only describe what differs from the default rather than the whole host, per-host values live as JSON overrides inside the cluster profile instead of answer files, and drift is flagged automatically every 24 hours. The vSphere docs add that changes go into a draft you can edit, pre-check and then apply, and that you can import a reference host's settings or a saved configuration document into a draft. The comparison post also points to a REST API with an OpenAPI specification and Terraform support through the vSphere provider, which makes it a natural fit for keeping cluster configuration in Git.
There are some boundaries to know before you rely on it. Configuration Profiles "does not manage the vSAN configuration", so vSAN settings stay with the vSAN APIs (Broadcom's blog mentions vSAN settings validation, but the docs are clear that the vSAN configuration itself isn't managed), and you can't enable it on clusters with DPU-backed hosts. On NSX-enabled clusters it needs NSX 9.0 or later with vCenter and ESX 9.0 or later; with 8.x hosts you can't enable it at all. Auto Deploy hosts can't boot straight onto a managed distributed switch, so the docs describe provisioning them on a standard switch first and migrating to the VDS afterwards. Broadcom's comparison also notes that Host Profiles can manage service states such as SSH or NTP start and stop, which Configuration Profiles can't.
For the transition itself, Vladan's StarWind walkthrough is a practical companion: make sure every host is compliant with the cluster image first, extract the settings from a reference host, import and review them, run the pre-check and then remediate. You can cancel part-way and resume later, but discarding your changes deletes the imported configuration. It was written in the 8.0 Update 3 era, so its line that NSX-enabled clusters aren't supported reflects 8.x; on 9.0 that's lifted as long as NSX is 9.0 or later.
In a nested lab this is well worth rehearsing, precisely because you can't undo it. Build a small cluster, enable Configuration Profiles from a reference host, then change a setting by hand on one host and watch how compliance reports it and what remediation does. Export the document once you're happy and keep it alongside your Terraform and Packer code, so the production cluster starts from a configuration you've already tested.
Based on Using vSphere Configuration Profiles to Manage Host Configuration at a Cluster Level (vSphere 9.0) Official VMware vSphere Configuration Profiles: A Comparison with VMware Host Profiles (VCF Blog) Official vSphere Configuration Profiles: Features & Migration Tips (StarWind)
Industry
Features & Technical Blogs One worth reading
- Beat the Ticking Clock: Continuous Security in the Era of AI Exploits VCF Blog 11 Nov Official Brandon Hahn walks through the VCF 9.1.1 patching toolkit: ESX live patching (including on TPM-enabled servers), vCenter Quick Patch with Reduced Downtime Upgrade as the fallback, express patches for VCF Management Services that can go on in any order unless the notes say otherwise, and automatic renewal of VMCA root and solution user certificates that expire within a year during management-plane upgrades. Apart from the vCenter figure there are no measured downtime numbers, so treat it as a map of the options rather than a benchmark.
Licensing, Business & Industry News Two stories
- VMware Cloud Foundation getting major update for AI Blocks & Files 9 Nov Press Chris Mellor rounds up the 4 November portfolio news (vSAN S3 object storage, VPC policy-based connectivity, native DR, compliance in VCF Operations and the AI Infrastructure Quickstart, estimated for Q1 of Broadcom's fiscal 2027) and asks whether it will slow moves to Nutanix and Proxmox, calling it "too little too late" for customers who have already left.
- Critical Xen Orchestra Flaws Exploited in Attacks SecurityWeek 11 Nov Press Not VMware, but relevant if you've moved some workloads to XCP-ng: Vates says an authentication bypass in Xen Orchestra before 6.9.2 and 6.10.1 is being exploited for admin access, with no CVE assigned yet. It's a reminder that a hypervisor's management plane deserves the same network isolation you'd give vCenter.
Sources (31)