HomeNewsletterCommunityToolsArchiveBlogAboutQuick Links Subscribe free
← Back to Blog
Security Windows 11SecurityBitLockerSecure BootPatch Tuesday

Windows 11 June 2026 Security Alert: Secure Boot Certificate Update and BitLocker Bypass Fix

IA
EndpointWeekly Team
26 June 2026

Microsoft's June 2026 Patch Tuesday delivered one of the most consequential Windows security updates in recent years. KB5094126 — released June 9, 2026 — bundles a long-overdue Secure Boot certificate rotation with a patch for an actively exploited BitLocker bypass vulnerability. If you manage Windows endpoints, this update demands attention beyond your standard patching runbook.

The Secure Boot Certificate Clock Has Run Out

The 2011-era Secure Boot certificates underpinning the Windows trusted boot chain were always time-limited. That time is now up. Microsoft Corporation KEK CA 2011 expires in late June 2026, with additional 2011 certificates expiring through October. With KB5094126, Microsoft automatically migrates eligible devices to the newer 2023 certificate set — but the rollout is phased and not guaranteed to complete on your first update cycle.

Why this matters beyond just certificate housekeeping

Once the 2011 KEK expires, Microsoft loses the ability to sign new DBX (Secure Boot revocation list) updates using the old key. Devices that haven't completed the certificate migration will stop receiving future revocations — meaning newly discovered bootkit vulnerabilities could go unblocked on unpatched systems.

The transition does not happen automatically for all devices the moment you push KB5094126. Microsoft uses a phased delivery model based on device health signals — high-confidence devices get the new certificates first. Enterprise environments should monitor completion separately from update compliance.

Administrators can verify certificate status in Windows Security → Device Security. The new 2023 certificates will appear in the Secure Boot database once the migration completes.

⚠ HP device owners: check BIOS first

HP's April 2026 BIOS update for premium commercial laptops and workstations has a known conflict with the Secure Boot certificate rotation — affected devices may boot into BitLocker recovery after installing KB5094126. Install the latest HP firmware from HP Support before deploying this update broadly.

CVE-2026-45585: BitLocker Bypass via Windows Recovery Environment

Separate from the certificate work, KB5094126 also patches CVE-2026-45585 — a BitLocker Security Feature Bypass vulnerability rated Important by Microsoft. The CVE allows an attacker with physical access to a target device to bypass BitLocker device encryption and gain access to encrypted data.

How the attack works

The vulnerability exploits the autofstx.exe entry in the BootExecute REG_MULTI_SZ value within the Windows Recovery Environment (WinRE) offline SYSTEM registry hive. Because BootExecute runs before normal OS protections engage, an attacker who boots the device into WinRE can execute arbitrary code in a high-privilege context — effectively bypassing the encryption layer that BitLocker provides.

Who is most at risk

This is a physical access vulnerability. The threat model applies most acutely to:

Microsoft explicitly calls out this scenario: "Microsoft recommends considering these mitigations if devices and data are at risk of being compromised or stolen — for example, if employees take their work devices home or on business travel."

Mitigation: interim script + full patch

Microsoft has published a remediation script as an interim measure. The script mounts the WinRE image, loads the offline SYSTEM registry hive, removes autofstx.exe from the BootExecute value, then re-seals WinRE to maintain BitLocker trust chain integrity. Exit code 0 confirms success; exit code 1 indicates a failure requiring manual review.

The permanent fix ships as part of KB5094126. Installing the June 2026 cumulative update is the recommended path. The security update preserves the mitigation behavior post-installation.

IT Admin action checklist

  • Deploy KB5094126 via your standard patching process — treat as high priority given the BitLocker CVE
  • Back up BitLocker recovery keys to Azure AD / Entra ID or your key management system before pushing the update
  • For HP commercial devices: deploy updated BIOS firmware before the cumulative update
  • Monitor Secure Boot certificate migration status separately from update compliance reporting
  • Verify WinRE remediation using the Microsoft-provided mitigation script on any devices that cannot immediately receive KB5094126
  • If KB5094126 causes issues (especially Low Latency Profile conflicts on Intel hybrid-core CPUs), deploy KB5095093 (June 23 preview) which resolves known post-KB5094126 regressions

What Else Shipped in KB5094126

Beyond security work, KB5094126 also delivers the Low Latency Profile feature — a CPU boost mechanism that momentarily elevates clock speeds in response to shell interactions like Start menu presses and application launches. Microsoft describes this as up to 40% faster perceived response for common tasks.

Note: the Low Latency Profile has a documented conflict on systems with Intel 13th Gen hybrid architectures (such as the i7-13850HX) where efficiency cores can become pinned at 100% utilization. This is resolved by KB5095093. Organizations with fleets of Intel 13th Gen hybrid-core devices should test KB5094126 in a controlled pilot before broad deployment and have the June 23 update ready as a follow-on.

Recommended Deployment Approach

Phase 1 — Pilot (Week 1–2)

Deploy to 5–10% of fleet. Include HP devices in separate cohort after firmware update. Monitor for BitLocker recovery events and Low Latency Profile conflicts.

Phase 2 — Broad (Week 3–4)

Roll out to remaining devices. Pair with KB5095093 for fleets with Intel hybrid-core CPUs. Verify Secure Boot certificate migration completion.

Official Microsoft References

Share this post
LinkedIn X / Twitter Reddit Bluesky

More from EndpointWeekly

Security
Autopatch Is Alerting on Expiring Secure Boot Certificates —…
Windows Autopatch has added a new alert: 'Secure Boot — certificate update required'.…
Security
Microsoft Purview DLP Now Scans Copilot Prompts in Real Time:…
Microsoft Purview DLP can now block Copilot from processing prompts that contain…
Security
Entra ID SSPR Change: Unregistered Phone Numbers Stop Working…
From September 7 2026, Microsoft Entra self-service password reset will only accept…