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

Broadcom has quietly folded Site Recovery Manager into VMware Cloud Foundation and vSphere Foundation subscriptions. KB 461219 says SRM stopped being sold on its own on 2 November, and existing subscribers can either wait for the 9.1.3 release, expected between February and April 2027, or pick up a term-limited key now that expires on 2 May 2027. If you protect anything with SRM, or have wanted to, it's worth ten minutes today. Perpetual VCF licences don't qualify.

There's no new VMSA today, and if vCenter still isn't patched for CVE-2026-59310 that remains the first job.

Elsewhere, William Lam shows vCenter Linking taking over from Enhanced Linked Mode, which is also today's deep dive, and VCF Operations gains a Diagnostics Content Pack that can ship new findings between releases. A Broadcom VMmark post mentions VCF 9.1.2 ahead of any release notes, and on the wider security front this week's Apache and NGINX HTTP/2 flaws join Java4Shell on the list of things to patch on your own servers.

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 One KB worth reading SRM is now part of VCF and VVF
  • Terraform & Packer Nothing new vcf 0.19.0 still covers VCF 9.1.1
  • Next deadline Today Explore on Tour London ends today

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 (or 8.0 U2f) 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 still has no fix version: hosts patched first reject their host-scoped licences and the licences eventually expire. The workarounds are a fresh License Server with migrated entitlements, or a different valid licence on the host.
  • This month If you use, renew or want Site Recovery Manager, decide between waiting for 9.1.3 and taking the interim key. Per KB 461219, the term-limited key from My Downloads in the Support Portal covers up to 10,000 VMs, can't be split, combined, upgraded or downgraded, replaces existing SRM keys in vCenter, and expires on 2 May 2027, so you'll need the Protection and Recovery 9.1.3 appliance and vCenter 9.1 or later before then. Perpetual VCF customers aren't eligible.
  • This month Patch the Apache, NGINX and Java services you run yourself, and leave the VMware appliances to Broadcom. Singapore's CSA says the Apache mod_http2 flaw CVE-2026-119618 is reportedly being actively exploited (Apache's fix is 2.4.71), F5 fixed two critical NGINX HTTP/2 flaws on 18 November in 1.30.7 and 1.31.9 per Wiz, and GreyNoise has seen Java4Shell exploitation attempts, per Tenable. Broadcom hasn't published a VMware impact statement on any of them yet, and its appliance policy KB is the reason not to patch packages on vCenter or SDDC Manager by hand.
  • Lab vCenter Linking is a good thing to try in a lab before you rely on it, because it needs ELM broken and a shared identity provider first. The VCF 9.1 docs say a vCenter in Enhanced Linked Mode can't join a linking group, and every vCenter needs the same IdP. William Lam used Keycloak, which has no SCIM, so he had to publish the user into vCenter by hand before granting permissions.

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 industry side, Broadcom still hasn't said whether any VMware product is affected by Java4Shell (CVE-2026-114938), by the Apache mod_http2 flaw CVE-2026-119618, which Singapore's CSA now says is reportedly being exploited, or by the two critical NGINX HTTP/2 flaws (CVE-2026-123633 and CVE-2026-123007) fixed on 18 November. The PHP project is also due to ship another critical security release today, per The Register. 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 One KB 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, KB 456235 on host-scoped licences still has no fix version, 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 461219: Access to Site Recovery Manager for existing VCF and VVF subscription customers Broadcom KB Undated Official Since 2 November, SRM (formerly VMware Live Site Recovery) is no longer sold on its own; it's included in VCF and VVF subscriptions, and new, renewal and expansion subscriptions bought since then get it automatically. Existing subscribers can wait for VCF or VVF 9.1.3, expected February to April 2027, when the entitlement is added for you (with Protection and Recovery 9.1.3 and vCenter 9.1 or later), or take a version 8.1 key from My Downloads now that covers up to 10,000 protected VMs and expires on 2 May 2027. Existing SRM entitlements stay valid for their term, and perpetual VCF licences aren't eligible.

Releases & Release Notes Nothing new

No new VCF builds have been indexed yet: TechDocs carries a 19 November notice that new 9.1.1 patches are available, but 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 (12 October) and vSAN File Services 9.1.1.0200 (26 October), and the release notes index has no 9.1.2 or 9.2 line, although Broadcom's VMmark post (below) already names VCF 9.1.2. Outside the core stack, ESXi 8.0 U3k is still the newest 8.0 patch, Avi 32.1.4 the newest 32.1 release, VKS 3.8 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. vcf 0.19.0 is still the one to use for VCF 9.1.1, per the README, and the vsphere provider 2.18.0 from 9 November is still the latest, with its storage_policy breaking change on vsphere_namespace. 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. The Avi provider's pool bug, issue #719, is still open with no response.

Automation & API Ecosystem Nothing new

All quiet on 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. If your pipelines sit behind Apache or NGINX, or run on Java 17 or later, this week's HTTP/2 and Java4Shell fixes apply to them.

Nested Lab Corner Nothing new

Nothing new for nested labs since Holodeck 9.1.1 on Monday. A lab is the right place to rehearse moving from Enhanced Linked Mode to vCenter Linking: snapshot the vCenters, break ELM, point them at one identity provider and link them in VCF Operations, as KB 436011 describes for VVF.

Deep Dive of the Day

vCenter Linking in VCF 9.1: what replaces Enhanced Linked Mode, and what it doesn't carry over

For years, Enhanced Linked Mode was how you got one vSphere Client view across several vCenters: they joined one SSO domain and replicated roles, tags and global permissions between them. In VCF 9 that changes. Broadcom's 9.0 guidance says plainly that "ELM is deprecated in VMware Cloud Foundation 9.0", and the 9.1 docs on vCenter Linking recommend linking through VCF Operations instead. As William Lam puts it, ELM still works today but will be removed in a future release, so it's worth understanding the replacement before an upgrade forces the issue.

vCenter Linking is a VCF Operations feature, not something configured inside vCenter. You create a group under Administration, Configurations, vCenter Linking, pick between 2 and 15 vCenter instances on 9.0 or later, and from then on you can log in to any member with the vSphere Client and see all of their inventories. A vCenter can only be in one group, you need working forward and reverse DNS between all members, and the person creating the group needs the vCenter Linking role in VCF Operations. Lam notes it's included with both VVF and VCF entitlements.

Identity is the part that catches people out. The 9.1 page requires a common identity provider on every vCenter in the group; Lam describes that as VCF Single Sign-On with a SAML2 or OIDC IdP in VCF, and the same IdP configured on each vCenter in VVF. Authentication comes from the IdP but authorisation stays local: "IDP user permissions are not shared between vCenter systems", so you grant permissions on each vCenter. Lam used Keycloak, which has no SCIM, so he had to publish the user into vCenter by hand before he could assign permissions; you can create the group without an IdP, but you won't see the linked inventory until the IdP and permissions are in place.

The biggest practical difference is what isn't synchronised. The 9.1 page says synchronisation of roles, tags and global permissions across linked vCenters "is not available" with VCF Operations-based linking. Lam's post adds that with a VCF entitlement, tags are synced across the group through VCF Operations, which fits VCF's central tag management, but the TechDocs page doesn't describe that. So if your automation, backup policies or storage policies depend on ELM-replicated tags or global roles, plan to manage those centrally or per vCenter before you break ELM, and check the behaviour on your own entitlement.

You can't run both. A vCenter that's part of ELM can't join a linking group, so ELM has to be broken first. On fleets upgraded from VCF 5.x, the 9.0 procedure uses the SDDC Manager API (a validation of a breakElmSpec, then a PATCH on the management domain) and it breaks ELM for every vCenter in the instance at once; you can't pick a subset. For VVF, KB 436011 describes powered-off snapshots of the vCenters, cmsso-util break-elm on each one, a common IdP, and then linking in VCF Operations.

In a nested lab, this is a cheap rehearsal: two small vCenters, a Keycloak or similar IdP and VCF Operations are enough to see the login flow, the per-vCenter permissions and the tag behaviour for yourself. In production, treat breaking ELM as a change with a rollback plan: snapshot first, list every role, tag category and global permission you rely on, and make sure your scripts and PowerCLI sessions don't assume one SSO domain before you take it away.

Industry

Features & Technical Blogs Four worth reading

  • vCenter Linking Replaces Enhanced Linked Mode (ELM) in VVF & VCF 9.x williamlam.com 18 Nov Community If you still rely on ELM for one login across several vCenters, this is the replacement. William Lam links two vCenters under a VVF entitlement from VCF Operations (Administration, Configurations, vCenter Linking), for 2 to 15 vCenters on 9.0 or later with a common SAML2 or OIDC identity provider, and says ELM, deprecated since 9.0, will be removed in a future release. He adds that a VCF entitlement also syncs tags across the group.
  • New Diagnostics Content Pack in VCF Operations 9.1 VCF Blog 18 Nov Official Diagnostics in VCF Operations 9.1 is now an engine plus a separately updated content pack, so Broadcom can ship new findings without a product release. The first pack, for 9.1.0 and 9.1.1, flags the VMSA-2026-0006 vCenter and ESX CVEs, the vCenter UUID case mismatch that breaks licensing (KB 440982, fixed in vCenter 9.1.0.0200) and expired OAuth2 client credentials (KB 414489). It's in the Solution Catalog; Broadcom suggests subscribing to KB 371661 for updates.
  • VCF 9.1 and 6th Gen AMD EPYC CPUs Achieve VMmark Leadership Scores VCF Blog 18 Nov Official The first VMmark results on AMD EPYC 9006 parts, on Dell PowerEdge servers. What matters for planning is that the results table lists a VCF 9.1.2 system and the post says "VCF 9.1.2 enables support for these new CPUs"; there are no 9.1.2 release notes on TechDocs yet, so if you're buying these CPUs, check the compatibility guide before you assume 9.1.1 will do.
  • VCF 9.1 VPC Networking, Part 1: From External Connection to Virtual Private Cloud VCF Blog 18 Nov Official The first of six parts, setting out the build order: External IP blocks and an External Connection in the default project, delegation to a project, the project Transit Gateway, the VPC and its profiles, then subnets. Useful gotchas: all External Connections on one Transit Gateway must be the same type, a VPC connects to only one Transit Gateway, and the Avi toggle needs a private IP block and an assigned Edge cluster.

Licensing, Business & Industry News One for VCF security teams

The licensing news of the day is SRM moving into VCF and VVF subscriptions (see KB articles above). Broadcom reports its fourth-quarter and fiscal 2026 results on Wednesday 9 December, per Broadcom Investor Relations.

  • BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server The Hacker News 16 Nov Press A reminder that old vCenters stay attractive. Citing Kaspersky ICS CERT, the report says attackers got in through an exposed SSH service, used Log4Shell (CVE-2021-44228) on a vCenter 7.0.3 server to get root, reached the hypervisor over SSH, planted a cron backdoor and went on to the victim's GitLab, Ansible, domain controllers and build-signing server. No new VMware flaw is involved; vSphere 7 left general support on 2 October 2025.

Community & Learning

Videos, Podcasts & Events New this week

VMware Explore on Tour London finishes today; the tour moves on to Washington, D.C. on 8 December and Sydney on 3–4 March 2027, and VMUG Netherlands holds its VCF Techcon on 1 December. 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 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, and Hands-on Labs are still moving from the HOL-26xx labs to HOL-27xx with VCF 9.1 content.

Sources (38)

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 →