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

The story worth your Sunday coffee is Kaspersky's write-up of a BlackNevas ransomware attack that, over ten days, wiped four ESXi hosts, both vCenter appliances and the backups behind them. No VMware vulnerability was involved: the attackers came in with credentials taken from elsewhere in the network, logged in to vCenter over SSH and used Host Profiles to switch SSH on across the hosts. That makes it a very practical checklist for how you guard vCenter and the accounts that run it.

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

Otherwise it's a quiet weekend, with no new patches, KBs or provider releases, and Virtually Speaking has a second KubeCon episode out. Today's deep dive picks up Kaspersky's main advice and looks at VCF Single Sign-On and the Identity Broker, and how to keep your VCF admin identities apart from everyday domain accounts.

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 this weekend
  • Terraform & Packer Nothing new vsphere 2.18.0 is still the newest release
  • Next deadline 3 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.
  • 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. Today's deep dive covers how VCF SSO lets you put MFA in front of vCenter and NSX logins.
  • 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.
  • 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. Kaspersky's BlackNevas investigation (see Industry below) involved no VMware vulnerability at all. 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 this weekend, 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 says fixes will come "in upcoming product releases" without naming versions.

Releases & Release Notes Nothing new

No new VCF patches this weekend. 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 (26 October). If you browse the VCF Operations patch list you'll see a 9.1.1.0200 entry: it gathers the Fleet lifecycle, SDDC lifecycle and Software depot 9.1.1.0200 updates from 12 October, not new binaries, and VCF Operations itself is still 9.1.1.0100. 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

VCF Single Sign-On and the Identity Broker: keeping your admin front door apart from the domain

Kaspersky's BlackNevas write-up is a reminder that most vCenter compromises don't start with a VMware bug. Its list of entry routes is mostly about identity: Active Directory integration abuse, credentials reused from Windows systems and credentials pulled out of backup servers. Its first recommendation is to treat vCenter as a Tier 0 asset, with dedicated admin identities, phishing-resistant MFA and virtualisation admin credentials kept separate from domain and workstation ones. In VCF 9 the place you put most of that into practice is VCF Single Sign-On, so it's worth knowing exactly what it covers and what it doesn't.

VCF SSO is set up after deployment from VCF Operations, under fleet management, and the single sign-on itself is handled by the VCF Identity Broker, which Broadcom's identity post notes was formerly known as VIDB. Per the VCF 9.1 docs, it works across "all VCF components except SDDC Manager and ESX": vCenter, NSX, VCF Operations, VCF Automation, VCF Operations for networks, VCF Operations orchestrator, VCF Operations HCX and Salt RaaS. The same post points out that VCF 9.0 no longer uses Enhanced Linked Mode for SSO, so vCenters have to be reconfigured to use VCF SSO rather than inheriting it.

On the identity side you have two broad choices. You can federate to an identity provider (Okta, Ping Identity, Microsoft Entra ID, Microsoft ADFS, Symantec Identity Security Platform, or any SAML 2.0 or OIDC provider), or connect a directory, Active Directory over LDAP or OpenLDAP. Users and groups arrive by SCIM 2.0, by just-in-time provisioning at first login, or by an AD/LDAP sync of the users and groups you choose; passwords are never synced. Broadcom's post says MFA can be enforced from the corporate identity provider and then applies across the VCF stack. That's the practical answer to Kaspersky's advice: with a straight directory connection, a vCenter login is only as strong as the domain password behind it, whereas a federated identity provider can demand phishing-resistant MFA for the same login. Note that you get one identity provider per Identity Broker instance.

The Identity Broker has two deployment modes. In instance mode it's deployed as a VCF management services component in the management domain of a VCF instance, the first one in your primary instance, with optional extra brokers in other instances. In embedded mode it's configured in the management domain vCenter, which the docs describe as typically used within a single VCF instance. Broadcom's post adds that running it as a multi-node cluster protects against a single node failure, which matters once every admin login depends on it; the Identity Broker detailed design guide has the rest of the trade-offs.

A few gotchas for production. SDDC Manager and ESX sit outside VCF SSO, so their local accounts, SSH and lockdown mode are still yours to manage, which is exactly the gap the BlackNevas attackers used on the hosts. Just-in-time users aren't deleted when you remove them from the identity provider, so prefer group-based role assignments and review them, and remember that roles are granted per component (vCenter and NSX each need their own mapping). In Gibson Virtualization's walkthrough the lab binds to AD with the domain Administrator account; in production you'd want a dedicated, least-privileged bind account instead. And if you've upgraded to 9.1.1, keep an eye on the Identity Broker certificate alerts in KB 456305.

In a nested lab, embedded mode is the natural fit for a single instance, and a small lab AD with a dedicated VCF admin group, as the walkthrough uses, is enough to practise group-based roles. Whatever you build, follow Broadcom's advice from the post: test vCenter and NSX logins through the Identity Broker before you move off older or local authentication sources, and keep a documented break-glass route for SDDC Manager and ESX, since SSO won't cover them.

Based on Identity Providers and Protocols Supported for VCF Single Sign-On (VCF 9.1) Official Deployment modes for VCF Single Sign-On (VCF 9.1) Official Bringing "Out-of-the-Box" Modern Identity to Your Infrastructure with VMware Cloud Foundation 9.0 (VCF Blog) Official VCF 9: Enable and configure SSO, Part 1 (Gibson Virtualization) Community Ransomware at the hypervisor layer (Kaspersky Securelist) Press

Industry One story to read

Licensing, Business & Industry News One story to read

  • Ransomware at the hypervisor layer: how attackers use ESXi and vCenter features for malicious purposes Kaspersky Securelist 13 Nov Press If you only read one thing this weekend, make it this. Kaspersky's Global Emergency Response Team describes a BlackNevas intrusion that took ten days from first access to destruction and hit four ESXi hosts, every VM on them, two vCenter appliances and the backups. No hypervisor flaw was exploited: the attackers logged in to the DR vCenter over SSH as root, planted MeshAgent and a Ligolo-ng tunnel disguised as a vmware-vdma service, then used Host Profiles to turn on SSH on the hosts so their sessions came from vCenter's own address. Backups were disabled and encrypted days before the wiper ran.
  • BlackNevas Ransomware Attacks VMware ESXi Servers, Destroying Virtual Machines and Backup Infrastructure GBHackers 14 Nov Press A shorter summary of the same investigation, with the defensive checklist pulled out: vCenter as a Tier 0 asset with dedicated admin identities and phishing-resistant MFA, alerts on Host Profile changes to SSH, remote syslog, backups run under identities separate from production Active Directory, and restores tested on the assumption that vCenter and AD are gone.

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 →