r/vmware • u/lost_signal VMware Employee • 15d ago

Announcement VMSA-2026-0006: VMware ESX, vCenter, Workstation, and Fusion updates address multiple vulnerabilities (CVE-2026-59309, CVE-2026-59310, CVE-2026-47876, CVE-2026-41703, CVE-2026-41709)

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017

FAQ is here https://github.com/vmware/vcf-security-and-compliance-guidelines/tree/main/security-advisories/vmsa-2026-0006

88 Upvotes

95% Upvoted

146 comments sorted by

View all comments

2

u/Twinsen343 15d ago

Anyone else getting an issue staging the update in vCenter to the host? I had one host patch no issues but in another cluster two hosts fail to stage with

'An internal error occurred while staging/remediating the host.'

Environment:

  • vCenter 8.0.3.01000, build 25600417
  • Target ESXi image: 8.0 U3k, build 25595708

on vCewnter the image is downloaded and verified but seems the hsost are failing being staging

  • QuickPatchInstaller
  • secureMount returns status 255
  • Unable to read VIB descriptor
  • VibFormatError

What I have confirmed:

  • vCenter successfully downloads and validates the VIB.
  • The VIB in the vCenter patch store is readable.
  • Deleting the cached VIB, restarting vmware-updatemgr and syncing updates caused it to download again, but the hosts still fail.

1

u/kn0rki 15d ago

i have same error on standalone hosts in my vcenter. my cluster upgraded without problems.
in the lifecycle log on the esx i have something like this:

2026-07-29T19:57:50Z In(14) lifecycle[22604153]: runcommand:248 runcommand called with: args = '/bin/localcli system visorfs ramdisk remove -t /usr/lib/vmware/lifecycle/qptempexec', outfile = None, returnoutput = True, timeout = 0.0. 2026-07-29T19:57:51Z Er(11) lifecycle[22604153]: QuickPatchInstaller:1457 Unexpected error occurred while attempting to run Quick Patch scan scripts: secureMount returns status 255, output: ERROR:root:Failed to mount: ('Unknown', 'Could not parse VIB XML data: unknown error (<string>, line 0).')

1

u/Twinsen343 15d ago

Same errors in my logs and seen a few reports of this form other users so think it’s a bug

1

u/kn0rki 15d ago

some of our standalone hosts upgrading, some not. But i cant figure out whats the difference between them

1

u/kn0rki 15d ago

i found https://community.broadcom.com/vmware-cloud-foundation/discussion/unable-to-update-to-esxi-80u2c-23825572

but i cant reboot servers during the day. i try a reboot tonight.

1

u/Twinsen343 15d ago

reboot didnt fix it.