Broadcom adds ESX 8.0 U3m capsule path for VM Secure Boot keys

A VM can still boot while its ability to accept future boot-trust updates is blocked. Broadcom has now documented an ESX 8.0 capsule update path for eligible Windows VMs with vTPM.

Conceptual virtual servers receiving a protected key capsule beneath a shield, illustrating boot trust maintenance.

What changed — November 19, 2026

Broadcom KB423893 replaces the earlier pending 8.x guidance with ESX 8.0 U3m (P10) and adds VMware Tools 12.5.5 to the documented capsule Platform Key (PK) update path. This is a material remediation change, not a newly reported intrusion. The original KB publication date is not verified; its explicit November 19 revision establishes this update. Last verified: November 19, 2026 ET.

Check actual VM trust state

Inventory Secure Boot, vTPM, virtual hardware, creation/template history and guest PK/KEK/DB certificates. The KB identifies Secure Boot VMs with outdated certificates—NULL PK, 2011-only KEK or DB—and hardware version 13, creation on hosts earlier than ESX 8.0 U2, or inherited affected template NVRAM, running an OS expecting updates. Its FAQ also directs review of Secure Boot VMs lacking Microsoft 2023 certificates. Product labels such as ESXi 7.x/8.x/9.x are not a universal affected-version matrix. Do not infer customer deployment or exposure from them.

An invalid PK blocks KEK remediation; missing 2023 KEK blocks future DBX updates signed solely by that key. Missing 2023 DB certificates can block newer signed boot components. Broadcom says existing guest operating systems continue booting after certificate expiry; this is not an immediate fleet boot-stop claim.

Documented capsule prerequisites

CheckVendor requirement
InfrastructureFor the new 8.x path, ESX 8.0 U3m (P10). The capsule procedure calls for upgrading vCenter and cluster hosts, a VM power-on on the updated host, and VM hardware version 14 or later. Follow the supported compatibility/upgrade path; no numeric build is inferred here.
Windows guestsServer 2025, 2022, 2019 or 2016; Windows 11 25H2, 24H2 or 23H2; Windows 10 64-bit 22H2, 21H2 or 1809.
Guest updatesJuly 2026 Windows cumulative update or later, plus Tools 12.5.5/13.1.5 or newer for most supported guests. Server 2016 and Windows 10 64-bit 22H2/1809 require Tools 13.1.6 or later.
Sequence and restartInstall the Windows cumulative update before Tools, except Server 2025 and Windows 11 24H2/25H2 allow the reverse order. Both update stages require system restarts. A yellow warning on the Platform Key Firmware driver requires an additional reboot.

Documentation caveat: the detailed guest table still describes support for Server 2016 and Windows 10 22H2/1809 as upcoming, while the release matrix and dated November 9 note specify Tools 13.1.6+. Confirm the supported package and guest path with Broadcom before those deployments. Download entitlement, package retrieval and installed customer builds were not verified.

Linux and legacy Windows with vTPM have no automated capsule solution in this KB. Use their separate supported manual procedure with its TPM/application precautions. The older vTPM-disabled SilentPK path is unchanged. An infrastructure upgrade alone does not complete guest PK, KEK, DB or DBX remediation.

MSP action sequence

Suggested priority: High for confirmed affected VMs, scheduled through change control. Inventory key state and eligible guests → prepare verified recovery materials and a pilot/rollback plan → apply the supported host, Windows and Tools sequence → verify the running versions, Platform Key Firmware status, PK and 2023 KEK/DB state, applicable DBX updates, successful boots and TPM/encryption-dependent workloads. Check affected templates as well as existing VMs.

Manual key changes can alter TPM measurements and affect BitLocker/LUKS. Follow the selected vendor procedure for snapshots, recovery keys and TPM-based application preparation. Do not treat alarm acknowledgement as remediation or disable security controls as a blanket workaround. No incident-driven containment or credential rotation is newly directed by this KB.

Evidence and limits

This certificate-transition KB supplies no CVE, vendor severity or CVSS score, and reports no new exploitation finding. There is no CVE-linked KEV addition or federal deadline for this item. Other source-access gaps remain open; this finding is not an all-clear across the monitored portfolio.

Broadcom KB423893: current requirements, procedures, FAQs and dated revision history.

Share this article