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.
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.
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.
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.
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 →
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.