Patch tracker / KB5082142
KB5082142: Windows Server 2022 Security Update (April 2026)
KB5082142 is a Critical security update for Windows Server 2022, released 2026-04-14. It closes 115 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 4 known issues: test it before broad deployment. It is the fifth largest of the 60 updates Microsoft shipped that month, by CVEs closed.
Before you deploy: Microsoft lists 4 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 115 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 Server 2022 has shipped since this one: KB5126655 (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 4 known issues with this update.
- Domain controllers might restart repeatedly after installing this update
- Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
- Windows Server Update Services (WSUS) does not display error details
KB5082142 is an unusually large Windows 10 1809 and Server 2019 rollup fixing 117 CVEs, including one already listed in the CISA Known Exploited Vulnerabilities catalog. The top flaw rates Critical at CVSS 9.8 with a 64 percent EPSS score, meaning exploitation is probable rather than theoretical, and any 1809 or Server 2019 host is exposed until patched.
Do this: Deploy KB5082142 to all Windows 10 1809 and Server 2019 systems now, prioritizing internet-facing servers given the confirmed KEV entry.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5082142
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5082142
- 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 117 to 116
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 KB5082142 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5082142 (checked 2026-09-10). Microsoft lists 4 known issues. Verify against the article before acting.
1. Domain controllers might restart repeatedly after installing this update
Symptom
After installing this update, domain controllers in environments with multiple domains in the forest that use Privileged Access Management (PAM), might experience LSASS crashes during startup. As a result, affected domain controllers might restart repeatedly, preventing authentication and directory services from functioning, and potentially rendering the domain unavailable.
Resolution
This issue is addressed in out-of-band update KB5091575 .
Note
If your Windows Server 2022 device is enrolled in hotpatching, you should instead install the OOB hotpatch update KB5091576 . This hotpatch OOB update is released through Windows Update and does not require the device to restart.
2. 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 ...
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
KB5082052
114 CVEs · Critical · exploitedKB5082060
120 CVEs · Critical · exploitedKB5082063
123 CVEs · Critical · exploitedKB5082123
106 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.