Patch tracker / KB5082052
KB5082052: Windows 11 Version 23H2 Security Update (April 2026)
KB5082052 is a Critical security update for Windows 11 Version 23H2, released 2026-04-14. It closes 114 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV), so it is urgent, and Microsoft lists 2 known issues: test it before broad deployment. It is the sixth largest of the 60 updates Microsoft shipped that month, by CVEs closed.
Before you deploy: Microsoft lists 2 known issues for this update.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Update summary
Fixes 114 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 3.5%. Among the top half of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Windows 11 Version 23H2 for ARM64-based Systems has shipped since this one: KB5126653 (2026-10-13). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 2 known issues with this update.
- Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
- Warnings related to Remote Desktop might not display correctly
KB5082052 is a large April 2026 rollup for Windows 10 1809 and Windows Server 2019 that closes 116 CVEs, topped by a Critical issue rated CVSS 9.8 with a 64 percent EPSS score. One of these CVEs is already on the CISA KEV list, meaning it is confirmed exploited in the wild, though none are currently tied to ransomware. Legacy 1809 endpoints and Server 2019 hosts running domain or infrastructure roles are the exposed population here.
Do this: Deploy KB5082052 to all Windows 10 1809 and Server 2019 systems this cycle, prioritizing the internet-facing and domain-role hosts because of the known-exploited CVE.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5082052
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5082052
- Released
- 2026-04-14
- Last changed
- 2026-10-15
- Changes tracked
- 8
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
- 2026-08-19 CVEs fixed 116 to 115
Recorded by Senserva on the dates shown, from the MSRC release feed. This is what moved and when, which neither the vendor advisory nor NVD publishes.
Check if KB5082052 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5082052 (checked 2026-09-10). Microsoft lists 2 known issues. Verify against the article before acting.
1. Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
Symptom
Some devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key on the first restart after installing this update.
This issue only affects a limited number of systems in which ALL of the following conditions are true. These conditions are unlikely to be found on personal devices not managed by IT departments.
BitLocker is enabled on the OS drive.
The Group Policy " Configure TPM platform validation profile for native UEFI firmware configurations " is configured, and PCR7 is included in the validation profile (or the equivalent registry key is set manually).
System Information ( msinfo32.exe ) reports Secure Boot State PCR7 Binding as " Not Possible ".
The Windows UEFI CA 2023 certificate is present in the device’s Secure Boot Signature Database (DB), making the device eligible for the 2023‑signed Windows Boot Manager to be made the default.
The device is not already running the 2023-signed Windows Boot Manager.
In this scenario, the BitLocker recovery key only needs to be entered once -- subsequent restarts will not trigger a BitLocker recovery screen, as long as the group policy configuration remains unchanged. For help finding your BitLocker recovery key, see the article, Find your ...
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
Scope and sources
- Affected products
- Also released in April 2026
KB5082060
120 CVEs · Critical · exploitedKB5082063
123 CVEs · Critical · exploitedKB5082123
106 CVEs · Critical · exploitedKB5082142
115 CVEs · Critical · exploitedKB5082198
86 CVEs · Critical · exploitedKB5082200
106 CVEs · Critical · exploitedKB5083768
119 CVEs · Critical · exploitedKB5083769
120 CVEs · Critical · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.