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

If you're still on vSAN's Original Storage Architecture and have been putting off ESA because it looked like a forklift job, Broadcom's Pete Koehler has published a way round it. VCF 9.1's datastore sharing lets you move hosts across one at a time and Storage vMotion everything over, without spare swing hardware, though for now it's meant for workload domains rather than the management domain.

There's no new VMSA today, but vCenter CVE-2026-123890 is still the one to patch first, and SecurityOnline reports that CISA added it to its exploited-vulnerabilities list on 20 November with a 23 November deadline for US federal agencies. On VCF 9.0 the fix, vCenter 9.0.2.0200, now has its own release notes.

Otherwise it's a quiet Saturday: the second part of Broadcom's VPC networking series, a lab hardware post from William Lam, a new Virtually Speaking episode recorded at KubeCon, and nothing new from the Terraform providers. The deep dive walks through that OSA-to-ESA migration and where it differs from Broadcom's KB.

This is an earlier briefing. Read today's Latest Tech News →

  • Security No new VMSA KEV listing reported; patch vCenter now
  • Releases & KBs vCenter 9.0.2.0200 notes Build 25901331, the VCF 9.0 fix
  • Terraform & Packer Nothing new vcf 0.19.0 still covers VCF 9.1.1
  • Next deadline 10 days VMUG NL VCF Techcon, 1 Dec

Key Takeaways

  • Urgent If any vCenter is still unpatched for CVE-2026-123890, that's the weekend job: 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5. VMSA-2026-0009.1 lists no workaround and it isn't Quick Patch-eligible. Mandiant reports exploitation since early September, and SecurityOnline reports CISA added it to the KEV catalogue on 20 November with a 23 November federal deadline [Press]; Broadcom's advisory doesn't state exploitation. Once patched, check your SSO administrators and VAMI SSH settings, as Help Net Security and Security.io both stress that a patch doesn't tell you whether someone already got in.
  • Before upgrading On vCenter 8.0 U3m or 9.0.2.0200, hold off on the move to VCF 9.1.1 until 9.1.2 arrives. Broadcom's FAQ says those fixes are "Back-in-Time" for 9.1.1. There's still no 9.1.2 release line on TechDocs, so patch now and plan the upgrade later.
  • This month Keep HTTP/2 switched off on VCF Operations, Aria Operations 8.18 and HCX until VMSA-2026-0010 has patches. Every row in VMSA-2026-0010 is still "Patch pending". KB 463005 and KB 463022 are the workarounds, and an upgrade turns HTTP/2 back on, so re-check afterwards.
  • Watch If an OSA-to-ESA move is on your roadmap, read Broadcom's new swing method alongside KB 432894 before you plan. The VCF blog avoids buying swing hosts by using VCF 9.1 datastore sharing, but it doesn't cover CNS volumes, file shares or iSCSI, and it isn't for the 9.1.1 management domain yet. KB 432894 reminds you that reusing a host means wiping its disks.

Security Advisories Latest four

No new VMSA today, and none of these four has been revised since Friday; Broadcom's advisory portal has the rest. Patch vCenter for CVE-2026-123890 first. Broadcom's advisory still makes no statement on exploitation, while Mandiant reports a China-linked group has used it since early September, per Help Net Security [Press], and SecurityOnline reports CISA added it to the KEV catalogue on 20 November with a federal deadline of 23 November [Press]. VMSA-2026-0006 has dropped out of the latest four but isn't finished: CVE-2026-59310 has been in CISA's KEV catalogue since 18 August and its fixes still apply. On the wider industry front, Broadcom still hasn't said whether VMware products are affected by Java4Shell (CVE-2026-114938) or the NGINX HTTP/2 flaws.

VMSA-2026-0009.1 Critical Open Rev .1 · 20 Nov 2026

The one to patch first. CVE-2026-123890 is an authentication bypass in the VMware Directory Service in vCenter: someone with network access can get an administrator session. The same advisory fixes three SDDC Manager flaws (SQL injection, command injection and a local privilege escalation to root) and a SAML token signature bypass in VMware Tools for Windows. CVSSv3 6.7 to 9.8, no workarounds. Broadcom thanks Mandiant for reporting the vCenter flaw; the advisory makes no statement on exploitation, though Mandiant reports it has been exploited since early September and SecurityOnline reports a CISA KEV addition on 20 Nov [Press]. Issued 19 Nov 2026; revision .1 on 20 Nov clarified the affected VMware Tools versions.

  • CVE-2026-123890 9.8 vCenter directory service auth bypass · KEV addition 20 Nov reported by press
  • CVE-2026-123891 8.1 SDDC Manager SQL injection
  • CVE-2026-123892 7.2 SDDC Manager command injection
  • CVE-2026-123893 6.7 SDDC Manager / VCF Installer privilege escalation
  • CVE-2026-123894 6.7 Tools for Windows SAML signature bypass

DoPatch 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). SDDC Manager is fixed in 9.1.1.0200 (already out since 12 Oct), 9.0.2.0100 and 5.2.5, and Windows VMs need Tools 13.1.5.0 or 12.5.5.

VMSA-2026-0008.2 Critical Open Rev .2 · 19 Nov 2026

The Node.js Brotli decoder flaw in SDDC Manager: critical (9.8) on 9.1.1.x and important (7.5) on 9.0.x, 9.1.0 and 5.2.x. Revision .2 on 19 Nov added VCF 5.2.5 as the fixed version for 5.2.x; 9.0.x, 9.1.0 and 9.1.1 are still "Patch pending". The VMSA-2026-0009 FAQ says its fixed versions include the VMSA-2026-0008 fixes, but the 0008 matrix doesn't list any 9.x fix, so go by the matrix. Press reports a CISA KEV addition for the underlying Brotli flaw on 27 Oct; the advisory makes no statement on exploitation. First issued 27 Oct 2026.

  • CVE-2026-111497 9.8 9.8 on SDDC Manager 9.1.1, 7.5 elsewhere · reported KEV 27 Oct

DoOn 5.2.x, move to VCF 5.2.5. On 9.1.1 keep KB 460732 in place, and on 9.0.x or 9.1.0 KB 460734, until Broadcom lists a fix.

VMSA-2026-0010 Critical Open Initial · 19 Nov 2026

The Apache HTTP Server mod_http2 heap corruption flaw reaches VCF Operations 9.x, Aria Operations 8.18.x (standalone and in VCF 5.x) and VCF Operations HCX 9.1.x, with a CVSSv3 of 9.8 for anyone with network access. Every row says "Patch pending", and there's a workaround for each. The advisory makes no statement on exploitation; Singapore's CSA said on 17 Nov the Apache flaw is reportedly being exploited.

  • CVE-2026-119618 9.8 Apache mod_http2 RCE

DoDisable HTTP/2 with KB 463005 on every VCF Operations or Aria Operations node and KB 463022 on HCX, then re-check after each upgrade.

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. No workarounds, and 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.

All VMware security advisories on Broadcom's support portal →

KB Articles & Known Issues Nothing new today

No new VMware KBs have appeared since Thursday's VMSA-2026-0009 and VMSA-2026-0010 batch. On the articles we follow, KB 457944 still points to vCenter 9.1.1.0100 for the missing Supervisor Control Plane VMs, KB 456235 on host-scoped licences after ESX-first patching still has no fix version, and KB 458671 and KB 452660 on NSX 9.1.1 are unchanged.

  • KB 432894: Transitioning a vSAN OSA cluster to a vSAN ESA cluster Broadcom KB Reference Official Not new, but it's the official companion to today's OSA-to-ESA post. It covers vSAN 8.0, 9.0 and 9.1, says a direct in-place upgrade from OSA to ESA isn't supported because the two use different data paths and on-disk formats, and gives two routes: a new ESA cluster alongside, or reusing hosts after evacuating them, deleting their disk groups and cleaning the disks, which permanently loses whatever was on them.

Releases & Release Notes One set of release notes

Nothing else has moved. On the 9.1.1 line vCenter 9.1.1.0200 (19 Nov) is still the only new patch, with ESX, NSX and VCF Operations at 9.1.1.0100 and SDDC Manager at 9.1.1.0200, per the 9.1.1.x patch index, and there's still no 9.1.2 release line.

  • VMware vCenter 9.0.2.0200 Broadcom TechDocs 19 Nov Official The VCF 9.0 fix for CVE-2026-123890 now has its release notes: build 25901331, dated 19 November, a 9.2 GB patch ISO applied through VCF Operations in a VCF fleet. It fixes only that CVE and lists no known issues; for upgrade paths onwards it points to the interoperability matrix, and Broadcom's FAQ says it blocks the move to 9.1.1 until 9.1.2.

Automation & IaC

Terraform & Packer Nothing new

Nothing new from the providers. vcf 0.19.0 is still the one to use for VCF 9.1.1, per the README, and vsphere 2.18.0, nsxt 3.12.1, vcfa 1.2.3, avi 32.1.4 and the vsphere 2.5.1 and vmware 2.1.7 Packer plugins are unchanged. If you drive storage policies or cluster creation through the vsphere provider, an OSA-to-ESA move means new clusters and datastores in your state, so plan the Terraform side before you start moving hosts.

Automation & API Ecosystem Nothing new

No new releases for VCF.PowerCLI 9.1.1, govmomi 0.56.2, vmware.vmware 2.13.0 or vmware.vmware_rest 5.1.0. A version report across every vCenter is still the most useful script to run this weekend.

Nested Lab Corner One for the home lab

If you want to rehearse the OSA-to-ESA swing in a nested lab, keep the lab vCenter patched to 9.1.1.0200 first; today's deep dive has the steps.

  • Quad-port remote KVM upgrade for my VCF lab William Lam 20 Nov Community William swapped the 2U monitor-and-keyboard tray in his VCF 9.x mini rack for a GL.iNet Comet X, a 1U four-port KVM, so he can rebuild his three Minisforum MS-A2 hosts remotely without a KVM per host. It can upload ISOs of up to 60 GB for virtual media; the downsides he notes are a low-resolution live preview and no way to share one USB device across hosts.
Deep Dive of the Day

Moving from vSAN OSA to ESA in VCF 9.1 without swing hosts

Most teams with vSAN's Original Storage Architecture (OSA) have the same blocker: Broadcom has always said there's no in-place upgrade to the Express Storage Architecture (ESA). KB 432894 puts it plainly, explaining that the two use different data paths and on-disk formats, so you either build a new ESA cluster alongside and Storage vMotion across, or reuse hosts by emptying them, deleting their disk groups and cleaning the disks first. The second route is fine on paper, but on a busy cluster it's hard to free enough hosts to build a usable ESA cluster without buying hardware.

Pete Koehler's post on the VCF blog fills that gap with what he calls a "decoupled swing migration". The trick is VCF 9.1 datastore sharing: an OSA cluster can mount an ESA cluster's datastore and the other way round. That lets compute and storage move separately. You take one host out of the OSA cluster (maintenance mode, remove its disk claims), put it in a new ESA cluster without claiming its disks, mount the OSA datastore on the ESA cluster and vMotion compute only onto it. Repeat until you have enough hosts, in his 20-host example eight, then claim their disks as an ESA storage pool, mount the ESA datastore back on the OSA cluster and Storage vMotion the VM objects across. The remaining hosts follow one at a time, and finally you turn on Automatic Rebalance. He notes that no more than one host's compute was offline at any point.

It's worth being clear about what this is and isn't. Koehler describes it as close in principle to an in-place upgrade, but it's still a migration: every VM's storage moves to a new datastore, and the disks you reuse are reclaimed into a new format. So the KB and the blog agree on the fundamentals, and the blog's contribution is the order of operations. Capacity matters most: several hosts have to leave the OSA cluster before you can claim the ESA pool, so the method suits larger clusters with plenty of free space (his example started at about 40% used and reached about 67% on the OSA side).

Then there are the things it won't move. The post says CNS first-class disks (Kubernetes persistent volumes), vSAN File Services shares and vSAN iSCSI volumes aren't handled and need their own migration before you retire OSA, and that you should turn off the vSAN Performance Service on the old cluster before decommissioning it. It's also "initially intended for VCF workload domains only", because the VCF 9.1.1 management-domain service VMs don't support Storage vMotion. Don't turn on Automatic Rebalance on the ESA cluster until the migration has finished.

Hardware is the other check. The blog says ESA-compatible hardware may mean only a change of storage devices to NVMe, so check each host against the Broadcom Compatibility Guide before you start. Independent write-ups such as McSherry Tech's comparison list stricter needs, including 25GbE networking and a minimum NVMe device count and size, so treat those as things to confirm against the official ReadyNode guidance rather than as settled numbers.

In a nested lab this is a good rehearsal because the risky parts are procedural: build a small OSA cluster, practise moving hosts and shared datastores across one at a time, and watch how vMotion behaves when compute and storage live in different clusters. In production, write the host order down, check where your Kubernetes volumes and file shares live first, and keep your Terraform or PowerCLI definitions in step, because the new ESA cluster and datastore are new objects as far as your code is concerned.

Based on Migrate from vSAN OSA to vSAN ESA in VCF 9.1 Without Extra Hardware Official KB 432894: Transitioning a vSAN OSA cluster to a vSAN ESA cluster Official vSAN ESA vs. OSA (McSherry Tech) Community

Industry

Features & Technical Blogs Three worth reading

  • Migrate from vSAN OSA to vSAN ESA in VCF 9.1 Without Extra Hardware VCF Blog 20 Nov Official Pete Koehler's "decoupled swing migration": move OSA hosts into a new ESA cluster one at a time, share datastores both ways and Storage vMotion the VMs across, with never more than one host's compute offline. It's aimed at workload domains for now and doesn't move CNS volumes, file shares or iSCSI; today's deep dive goes through it.
  • VCF 9.1 VPC Networking, Part 2: IP blocks, external connections, transit gateways, subnets and NAT VCF Blog 19 Nov Official The second of six parts from Syed Qamar and Abhilash Pillai (after Part 1 on 18 November), and a clear map of how the VPC objects fit: the four IP block types, centralised and distributed external connections (distributed VXLAN from 9.1.1), the connectivity profile as "the contract" between a VPC and a transit gateway, the three subnet access modes and the NAT options. One lab gotcha: a centralised connection used by a transit gateway in one project can't be shared with a second project.
  • From AI experimentation to production: key takeaways from KubeCon North America 2026 VCF Blog 20 Nov Official Natalie Fisher's round-up: the conversation has moved from whether Kubernetes can run AI to how to run it under existing governance. It notes the Kubernetes AI Conformance Program now has 40 certified platforms, with VKS among them, and recaps the VM API joining the CNCF Sandbox.

Licensing, Business & Industry News One worth reading

Broadcom reports its fourth-quarter and fiscal 2026 results on Wednesday 9 December, per Broadcom Investor Relations.

  • VMware vCenter zero-day requires a compromise hunt, not patch-only closure Security.io 20 Nov Press A useful framing for anyone reporting upwards: because the attackers created SSO administrators and took SAML signing material, patching closes the door but doesn't prove nobody came through it. It suggests patching within 24 hours and reaching a compromise decision within 72, which is its own advice rather than Broadcom's or CISA's.

Community & Learning

Videos, Podcasts & Events One new episode

VMUG Netherlands holds its VCF Techcon on 1 December, VMware Explore on Tour reaches Washington, D.C. on 8 December and Sydney on 3–4 March 2027, and VMware Explore 2027 is at Resorts World Las Vegas on 10–13 May 2027, with registration opening on 12 January.

Certification & Learning Nothing new

No exam changes this week. The role-based VCF 9 VCAP exams, Administrator (3V0-11.26), Architect (3V0-12.26) and Support (3V0-13.26), are unchanged.

Sources (19)

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 →