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

Friday edition · archive

Check Point Research says attackers who broke into Check Point gateways through the PHP2Shell flaws later moved to a VMware ESXi host over SSH, signed in with vpxuser, the service account vCenter uses to manage hosts, and ran a wiper. No VMware vulnerability was involved, and the report doesn't say how they got the vpxuser credentials, but it's a pointed reminder that SSH into your hosts should be switched off or tightly fenced. That's the subject of today's longer Friday deep dive on lockdown mode.

There's no new VMSA today, and vCenter CVE-2026-59310 is still the one to patch first, with SDDC Manager still waiting for its Brotli fix.

Otherwise the week ends quietly: no new VCF 9.1.1 patches and no new Terraform or Packer releases. Broadcom has explained how AI ReadyNodes are certified and how its engineers fixed flaws in etcd, Pinniped and Velero that reach you through VKS, Virtually Speaking has a KubeCon episode out, and there's a correction to our license server build. The week in review is at the top.

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 Two KBs worth knowing Plus a correction to the license server build
  • Terraform & Packer Nothing new vsphere 2.18.0 is still the newest release
  • Next deadline 5 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 Check which of your ESX hosts accept SSH, from where, and who is on their lockdown exception lists. In the Check Point report the attackers reached ESXi over SSH as vpxuser. The vSphere 9.0 docs say that with lockdown mode on, SSH and the ESXi Shell are open only to DCUI.Access users and Exception Users with administrator privileges, so a host in lockdown with SSH stopped closes that particular door.
  • 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.
  • Lab If host commissioning on VCF 9.1.1 fails the vSAN HCL check on NVMe hosts, look at Intel VMD first. KB 459770 traces HOST_VSAN_HCL_VALIDATION_FAILURE to Intel Volume Management Device being enabled in the BIOS and the kernel. Disabling VMD is the fix; skipping the HCL check is the documented stop-gap, which is fine in a lab and worth avoiding in production.
  • 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).

Week in Review The week's top five

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, the PHP2Shell flaws are back in the news because of the Check Point gateway attacks; Broadcom's KB 459989 still says there are "zero affected products in the VMware Cloud Foundation product line". 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 →

Corrections One correction

  • The license server has been patched to 9.1.1.0100 Broadcom TechDocs 12 Oct Official The VCF license server is on 9.1.1.0100, build 25795080, released on 12 October alongside VCF Operations 9.1.1.0100, not the 9.1.1.0 GA build 25679819 shown in the Current builds table in recent briefings, including 12 Nov. The VCF Operations 9.1.1.0100 release notes say the license server and cloud proxy are patched automatically when you apply the VCF Operations patch.

KB Articles & Known Issues Two KBs worth knowing

Nothing has moved on the articles we follow. 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 future releases without naming any. KB 458671 (NSX Manager startup with host-based 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 457944 still points to vCenter 9.1.1.0100 for the missing Supervisor Control Plane VMs.

  • KB 459770: SDDC Manager host commissioning fails with HOST_VSAN_HCL_VALIDATION_FAILURE due to uncertified SSDs Broadcom KB Official Worth knowing if you're adding NVMe hosts to VCF 9.1.1: commissioning fails the vSAN HCL precheck when Intel Volume Management Device is enabled in both the BIOS and the ESX kernel (the drives show the iavmd driver). The fix is to disable VMD in the BIOS; if you must keep it, you can skip the HCL check in the wizard or with skipHclCompatibilityPrecheck in the API payload. One caution: the Dell steps in the article say to set VMD Mode to "Enabled", which contradicts the fix, so check before you save.
  • KB 455830: ESXi host hits PSOD during vMotion in NSX Broadcom KB Official A race between a timer callback and port disconnect clean-up can crash a host during vMotion of VMs with switch security on their ports, mostly in scaled environments. There's no workaround; it's fixed in NSX 4.2.5 and NSX 9.1.1, which is one more reason not to linger on older NSX 4.2.x or 9.0 builds.

Releases & Release Notes Nothing new

No new VCF patches this week. 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 Oct), and the VCF 9.1 release notes list no line beyond 9.1.1. On vSphere 8, ESXi 8.0 Update 3k is still the newest update, and Avi Load Balancer 32.1.4 and VMware Tools 13.1.6 are unchanged.

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

A quiet week 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

Lockdown mode, SSH and vpxuser: closing the side doors into ESX

This week's Check Point report has a detail that should make every vSphere admin pause: after compromising a firewall, the attackers "pivoted from the compromised gateway to a VMware ESXi host over SSH, authenticating with the vpxuser service account", then ran a wiper. The report doesn't say how they got that credential, and no VMware flaw was involved. What it does show is that a reachable SSH service on a host is a door, and that the account behind it doesn't have to be root. So for a longer Friday piece, let's walk through the controls that decide who can get a shell on ESX at all.

Start with vpxuser itself. Broadcom's KB 453134 describes it as "the service account vpxuser is used by vCenter Server to manage and communicate with ESXi hosts". You never set its password: vCenter generates it and, per KB 320773, changes it automatically every 30 days, controlled by the vCenter advanced setting VirtualCenter.VimPasswordExpirationInDays. Both KBs are written for vSphere 8.0, but the mechanism is the one your 9.x hosts inherit.

That rotation has a couple of gotchas that bite in real environments. KB 320773 is blunt that "VMware does not recommend increasing the value", and that the host's Security.PasswordMaxDays "should always be a greater value" than vCenter's rotation interval. KB 453134 lists the ways it goes wrong: a host password policy shorter than 30 days, a host left in maintenance mode longer than its maximum password age, a host unreachable for more than 30 days, or a vCenter interval set longer than the host's. The symptom is a host going "Not Responding", and the fix is usually to correct the policy and reconnect the host with root.

Now the main control: lockdown mode. The vSphere 9.0 docs describe it simply: "In lockdown mode, operations must be performed through vCenter by default." There are two levels. Normal lockdown can be switched on or off from the Direct Console User Interface (DCUI) as well as the vSphere Client; strict lockdown can be changed only from the vSphere Client, because it stops the DCUI service altogether.

The part that matters for this week's story is what happens to SSH and the ESXi Shell. According to the lockdown mode behaviour page, in both normal and strict mode, shell and SSH access (if those services are running) is limited to users in the DCUI.Access advanced setting and to Exception Users who have administrator privileges on the host: "For all other users, ESXi Shell or SSH access is deactivated." Existing sessions for anyone else are closed when the host enters lockdown. By that rule, a host in lockdown mode wouldn't accept an SSH login as vpxuser unless someone had added it to one of those lists.

Lockdown mode doesn't cut vCenter off, which is the point of it. The same page says the vSphere Web Services API stays open to vCenter (vpxuser), to Exception Users according to their permissions, and to vCloud Director (vslauser) where present, and that privileged users can still manage the host through vCenter, the vSphere Client or the SDK. It also notes that "All access is logged for both strict and normal lockdown mode", which is worth wiring into your log forwarding.

The two lists are where lockdown mode quietly gets undone. The exception users page says the Exception Users list "is meant for service accounts that perform very specific tasks, and not for administrators", such as a backup agent, and warns that "Adding administrator users to the Exception Users list defeats the purpose of lockdown mode." DCUI.Access "is meant for a catastrophic failure of vCenter"; Broadcom suggests removing root from it in favour of a named local account whose password lives in a safe, and warns that anyone on that list "can change lockdown mode settings regardless of their privileges". Only local ESX users can go on it, not Active Directory accounts.

Christian Mohn's ESXi hardening checklist on vNinja [Community] puts the wider context well: "ESXi does not support MFA, SAML, OIDC, or FIDO2 for any access path", so SSH, the DCUI and the Host Client all sit below vCenter's identity federation. He suggests normal lockdown for most environments (strict also removes the DCUI you might want for break-glass recovery), reviewing every Exception Users entry as "a documented bypass of Lockdown Mode", keeping management interfaces on a dedicated management network, and watching UserLoginSessionEvent entries for DCUI logins. He also scripts the change across clusters with ChangeLockdownMode("lockdownNormal") through the host access manager.

For production, the practical recipe is short. Leave SSH and the ESXi Shell stopped unless you're actively troubleshooting, turn on normal lockdown, keep Exception Users to genuine service accounts, give DCUI.Access one named break-glass account, and make sure only your admin network can reach host management at all, so a compromised firewall or jump box isn't one SSH hop from your hypervisors. Thursday's deep dive on vSphere Configuration Profiles is a reminder that host settings like these are better enforced centrally than set by hand.

In a nested lab the trade-offs are different, and that's fine. You'll probably want SSH on while you build and break things, and strict lockdown on a nested host you can only reach through a console window is a quick way to lock yourself out. The useful lab exercise is to turn normal lockdown on, confirm that vCenter, your automation and your backup tool still work, and see which of them complain. Whatever fails is something that's talking to the host directly, and it's much better to find that in a lab than during a production change.

Based on Configuring and Managing Lockdown Mode on ESX Hosts (vSphere 9.0) Official Lockdown Mode Behavior (vSphere 9.0) Official Specifying Accounts with Access Privileges in Lockdown Mode Official KB 453134: vpxuser password expiration Official KB 320773: vpxuser expiry settings Official ESXi Has No MFA: A Practical Hardening Checklist (vNinja) Community PHP2Shell Exploitation on Check Point Gateway Press

Industry

Features & Technical Blogs Two worth reading

  • Strengthening Cloud-Native Security Through Upstream Collaboration VCF Blog 12 Nov Official If you run VKS, this tells you where some recent fixes came from: Broadcom engineers found and fixed an etcd flaw (CVE-2026-73500, backported to 3.5.33, 3.6.14 and 3.7.1) and a Pinniped credential-handling issue (CVE-2026-59269, fixed in 0.47.0), both shipped in the VKr October releases, plus two Velero advisories fixed in 1.18.3 and included in VKS Add-ons v3.7.0+20260924. Worth checking your VKr and add-on versions against those.
  • Unlocking AI Performance: Benefits and Certification of VMware AI ReadyNodes VCF Blog 12 Nov Official A clear explanation of what makes a server an AI ReadyNode: four certification phases, from vSphere server certification through GPU functional testing, and a separate "AI Ready Node (Server + GPU)" listing in the Broadcom Compatibility Guide. A server that only appears on the DirectPath I/O list is meant for VDI and similar workloads, not AI, so check the right list before you buy.

Licensing, Business & Industry News One story

  • PHP2Shell Exploited in Destructive Check Point Gateway Attacks SecurityWeek 13 Nov Press SecurityWeek's write-up of the Check Point Research report: a first wave from 30 Oct hit Israeli organisations and was destructive, a second from 2 Nov spread across several countries without destruction. After rooting the gateways with PHP2Shell and CVE-2026-123039, the attackers moved to an ESXi host over SSH as vpxuser and ran a wiper that leaves a DREAM_ANNEXATION.txt note. Check Point's own advisory points customers to its November Jumbo Hotfix.

Community & Learning

Community Picks Nothing new

No new posts from the usual VMware bloggers since Monday. If you missed it, William Lam's quick tip on checking VCF download checksums against the manifest files is still worth a bookmark.

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 (40)

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 →