Patch tracker / KB5082200

KB5082200: Windows Server 2019 Security Update (April 2026)

KB5082200 is a Critical security update for Windows Server 2019, released 2026-04-14. It closes 107 CVEs with a maximum CVSS of 9.8. The most likely of them to be attacked is CVE-2026-20930, which FIRST.org rates at 56% probability of exploitation in the next 30 days.

Update summary

Critical

2026-04-14

Released

107

CVEs fixed

9.8

Max CVSS

Critical

Severity

Deploy this cycle

Fixes 107 CVEs for Windows Server 2019. No confirmed in-the-wild exploitation in this set today.

Fixes 107 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 56%. Among the top 25% of tracked Microsoft updates by EPSS exploit probability.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

A newer security update for Windows 10 Version 1809 for 32-bit Systems has shipped since this one: KB5089548 (2026-07-14). 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.

Senserva found thisread these before you deploy broadly

Microsoft documents 1 known issue with this update.

Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5082200 Microsoft support article

Senserva AI Opinion for KB5082200

KB5082200 is a large April 2026 rollup for Windows 10 Version 1809 and Windows Server 2019, closing 108 CVEs including one rated Critical at CVSS 9.8 with a 64 percent EPSS score. At least one of these CVEs is listed in the CISA Known Exploited Vulnerabilities catalog, so exposure is confirmed in the wild rather than theoretical, though none are currently tied to ransomware. Any 1809 or Server 2019 host that has not taken this cumulative update is missing all 108 fixes at once.

Do this: Deploy KB5082200 to all Windows 10 1809 and Windows Server 2019 systems now, prioritizing internet-facing Server 2019 hosts because of the confirmed KEV-listed and CVSS 9.8 vulnerabilities.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for KB5082200

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin triaging Microsoft updates. Facts for KB5082200 (source: https://senserva.com/kb/5082200.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- Update: KB5082200, Windows Server 2019, released 2026-04-14
- Severity: Critical; fixes 107 CVEs, max CVSS 9.8
- Actively exploited (CISA KEV): no
- CVEs include: CVE-2025-64720, CVE-2025-65018, CVE-2026-0390, CVE-2026-20806, CVE-2026-20928, CVE-2026-20930, CVE-2026-23670, CVE-2026-25250 and 99 more
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5082200
Using only these facts plus your general knowledge, tell me: 1) How urgent this update is and why, in two sentences. 2) Which systems should get it first. 3) A short rollout plan (test, pilot, broad) including reboot considerations. 4) What to verify after deployment.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for KB5082200

Released: 2026-04-14
Last changed: 2026-07-29
Changes tracked: 2

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.

Check if KB5082200 is installed

Elevated PowerShell. No output means it is not installed.

# Is KB5082200 installed? (elevated PowerShell)
Get-HotFix -Id KB5082200 -ErrorAction SilentlyContinue

# Across many machines (replace the names):
Invoke-Command -ComputerName SERVER01,SERVER02 {
  Get-HotFix -Id KB5082200 -ErrorAction SilentlyContinue
} | Select-Object PSComputerName, HotFixID, InstalledOn

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5082200 (checked 2026-07-28). Verify against the article before acting.

Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key

Symptoms

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 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.

CVE	Severity	CVSS	EPSS	Exploited
CVE-2025-64720	Critical	9.8	56%	No
CVE-2025-65018	Critical	9.8	56%	No
CVE-2026-0390	Critical	9.8	56%	No
CVE-2026-20806	Critical	9.8	56%	No
CVE-2026-20928	Critical	9.8	56%	No
CVE-2026-20930	Critical	9.8	56%	No
CVE-2026-23670	Critical	9.8	56%	No
CVE-2026-25250	Critical	9.8	56%	No
CVE-2026-26151	Critical	9.8	56%	No
CVE-2026-26152	Critical	9.8	56%	No
CVE-2026-26153	Critical	9.8	56%	No
CVE-2026-26155	Critical	9.8	56%	No
CVE-2026-26156	Critical	9.8	56%	No
CVE-2026-26159	Critical	9.8	56%	No
CVE-2026-26160	Critical	9.8	56%	No
CVE-2026-26161	Critical	9.8	56%	No
CVE-2026-26162	Critical	9.8	56%	No
CVE-2026-26163	Critical	9.8	56%	No
CVE-2026-26167	Critical	9.8	56%	No
CVE-2026-26168	Critical	9.8	56%	No
CVE-2026-26169	Critical	9.8	56%	No
CVE-2026-26170	Critical	9.8	56%	No
CVE-2026-26172	Critical	9.8	56%	No
CVE-2026-26173	Critical	9.8	56%	No
CVE-2026-26174	Critical	9.8	56%	No
CVE-2026-26175	Critical	9.8	56%	No
CVE-2026-26176	Critical	9.8	56%	No
CVE-2026-26177	Critical	9.8	56%	No
CVE-2026-26178	Critical	9.8	56%	No
CVE-2026-26180	Critical	9.8	56%	No
CVE-2026-26182	Critical	9.8	56%	No
CVE-2026-26184	Critical	9.8	56%	No
CVE-2026-27906	Critical	9.8	56%	No
CVE-2026-27908	Critical	9.8	56%	No
CVE-2026-27909	Critical	9.8	56%	No
CVE-2026-27910	Critical	9.8	56%	No
CVE-2026-27911	Critical	9.8	56%	No
CVE-2026-27914	Critical	9.8	56%	No
CVE-2026-27915	Critical	9.8	56%	No
CVE-2026-27916	Critical	9.8	56%	No
CVE-2026-27917	Critical	9.8	56%	No
CVE-2026-27918	Critical	9.8	56%	No
CVE-2026-27919	Critical	9.8	56%	No
CVE-2026-27920	Critical	9.8	56%	No
CVE-2026-27921	Critical	9.8	56%	No
CVE-2026-27922	Critical	9.8	56%	No
CVE-2026-27923	Critical	9.8	56%	No
CVE-2026-27924	Critical	9.8	56%	No
CVE-2026-27925	Critical	9.8	56%	No
CVE-2026-27926	Critical	9.8	56%	No
CVE-2026-27927	Critical	9.8	56%	No
CVE-2026-27929	Critical	9.8	56%	No
CVE-2026-27930	Critical	9.8	56%	No
CVE-2026-27931	Critical	9.8	56%	No
CVE-2026-32068	Critical	9.8	56%	No
CVE-2026-32069	Critical	9.8	56%	No
CVE-2026-32070	Critical	9.8	56%	No
CVE-2026-32071	Critical	9.8	56%	No
CVE-2026-32072	Critical	9.8	56%	No
CVE-2026-32073	Critical	9.8	56%	No
CVE-2026-32074	Critical	9.8	56%	No
CVE-2026-32075	Critical	9.8	56%	No
CVE-2026-32077	Critical	9.8	56%	No
CVE-2026-32078	Critical	9.8	56%	No
CVE-2026-32079	Critical	9.8	56%	No
CVE-2026-32081	Critical	9.8	56%	No
CVE-2026-32082	Critical	9.8	56%	No
CVE-2026-32083	Critical	9.8	56%	No
CVE-2026-32084	Critical	9.8	56%	No
CVE-2026-32085	Critical	9.8	56%	No
CVE-2026-32086	Critical	9.8	56%	No
CVE-2026-32087	Critical	9.8	56%	No
CVE-2026-32088	Critical	9.8	56%	No
CVE-2026-32089	Critical	9.8	56%	No
CVE-2026-32090	Critical	9.8	56%	No
CVE-2026-32091	Critical	9.8	56%	No
CVE-2026-32093	Critical	9.8	56%	No
CVE-2026-32149	Critical	9.8	56%	No
CVE-2026-32150	Critical	9.8	56%	No
CVE-2026-32151	Critical	9.8	56%	No
CVE-2026-32153	Critical	9.8	56%	No
CVE-2026-32154	Critical	9.8	56%	No
CVE-2026-32155	Critical	9.8	56%	No
CVE-2026-32156	Critical	9.8	56%	No
CVE-2026-32157	Critical	9.8	56%	No
CVE-2026-32158	Critical	9.8	56%	No
CVE-2026-32159	Critical	9.8	56%	No
CVE-2026-32160	Critical	9.8	56%	No
CVE-2026-32162	Critical	9.8	56%	No
CVE-2026-32163	Critical	9.8	56%	No
CVE-2026-32164	Critical	9.8	56%	No
CVE-2026-32165	Critical	9.8	56%	No
CVE-2026-32181	Critical	9.8	56%	No
CVE-2026-32183	Critical	9.8	56%	No
CVE-2026-32212	Critical	9.8	56%	No
CVE-2026-32214	Critical	9.8	56%	No
CVE-2026-32215	Critical	9.8	56%	No
CVE-2026-32217	Critical	9.8	56%	No
CVE-2026-32218	Critical	9.8	56%	No
CVE-2026-32225	Critical	9.8	56%	No
CVE-2026-33098	Critical	9.8	56%	No
CVE-2026-33099	Critical	9.8	56%	No
CVE-2026-33100	Critical	9.8	56%	No
CVE-2026-33104	Critical	9.8	56%	No
CVE-2026-33824	Critical	9.8	56%	No
CVE-2026-33827	Critical	9.8	56%	No
CVE-2026-33829	Critical	9.8	56%	No

Scope and sources

Affected products

Also released in April 2026

Authoritative references

Official KB5082200 page (Microsoft Support)Microsoft Update Catalog Microsoft Security Update Guide

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

KB5082200: Windows Server 2019 Security Update (April 2026)

Update summary

Full tracking and change history for KB5082200

Check if KB5082200 is installed

Known issues, from Microsoft

CVEs fixed by this update

Scope and sources

KB5002853

KB5002854

KB5002861

KB5082052

KB5082060

KB5082063

KB5082123

KB5082142