Patch tracker / KB5082198

KB5082198: Windows Server 2019 Security Update (April 2026)

KB5082198 is a Critical security update for Windows Server 2019, released 2026-04-14. It closes 87 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. The most likely of them to be attacked is CVE-2026-0390, which FIRST.org rates at 73% probability of exploitation in the next 30 days.

Update summary

CriticalCISA KEV
2026-04-14
Released
87
CVEs fixed
9.8
Max CVSS v3
Critical
Severity
Deploy now
This update fixes vulnerabilities confirmed exploited in the wild.

Fixes 87 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 73%. 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: KB5094041 (2026-08-11). 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.

  • Domain controllers might restart repeatedly after installing this update

The full text, quoted from Microsoft

Senserva AI Opinion for KB5082198

KB5082198 is a large April 2026 rollup fixing 88 CVEs, including one already listed in the CISA KEV catalog (exploited in the wild, though not tied to ransomware) and a Critical flaw rated CVSS 9.8 with a 64 percent EPSS exploitation-likelihood score. It applies to Windows 11 26H1 on both ARM64 and x64 plus the older Windows 10 1809 on 32-bit systems, so both new and legacy fleets are exposed. The combination of a confirmed exploited CVE and a near-worm-grade Critical bug makes this a priority cycle rather than a routine one.

Do this: Deploy KB5082198 immediately to internet-facing and legacy Windows 10 1809 hosts first, then complete the rest of the Windows 11 26H1 fleet within the standard maintenance window.

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

Senserva AI Opinion and rich prompt for KB5082198

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

Full tracking and change history for KB5082198

Released
2026-04-14
Last changed
2026-08-24
Changes tracked
5

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.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is the single recorded change on 2026-08-19, when the CVE fix count for KB5082198 dropped from 88 to 87. This slight downward revision suggests a minor correction rather than expanded coverage. With only one data point and a small decrease, there is no urgent trend here, so proceed with standard patch validation.

  • 2026-08-19 CVEs fixed 88 to 87

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 KB5082198 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5082198 (checked 2026-08-27). Verify against the article before acting.

Domain controllers might restart repeatedly after installing this update

Symptoms

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

Remote Desktop security warnings might not display correctly

Symptoms

After installing this update, the security warning that appears when opening Remote Desktop (RDP) files might not display correctly in some cases.

This issue might occur when you use more than one monitor with different display scaling settings (for example, one display set to 100% and another set to 125%). When this happens, the warning window might show overlapping text or partially hidden buttons, which can make the message difficult to read or interact with.

Resolution

This issue is resolved in Windows updates released on and after May 12, 2026 (such as KB5087537 ). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.

Applies to: Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise 2016 LTSB

This ...

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.

CVESeverityCVSSEPSSExploited
CVE-2026-33824Critical9.873%KEV
CVE-2026-20928Critical9.873%No
CVE-2026-26175Critical9.873%No
CVE-2026-33829Critical9.873%No
CVE-2026-26167High8.873%No
CVE-2026-26178High8.873%No
CVE-2026-32157High8.873%No
CVE-2026-32225High8.873%No
CVE-2026-27928High8.773%No
CVE-2026-32091High8.473%No
CVE-2026-33827High8.173%No
CVE-2026-27912High8.073%No
CVE-2026-33826High8.073%No
CVE-2026-26156High7.873%No
CVE-2026-26159High7.873%No
CVE-2026-26160High7.873%No
CVE-2026-26162High7.873%No
CVE-2026-26163High7.873%No
CVE-2026-26168High7.873%No
CVE-2026-26170High7.873%No
CVE-2026-26176High7.873%No
CVE-2026-26180High7.873%No
CVE-2026-26183High7.873%No
CVE-2026-27909High7.873%No
CVE-2026-27910High7.873%No
CVE-2026-27911High7.873%No
CVE-2026-27914High7.873%No
CVE-2026-27915High7.873%No
CVE-2026-27916High7.873%No
CVE-2026-27919High7.873%No
CVE-2026-27920High7.873%No
CVE-2026-27923High7.873%No
CVE-2026-32077High7.873%No
CVE-2026-32089High7.873%No
CVE-2026-32090High7.873%No
CVE-2026-32154High7.873%No
CVE-2026-32164High7.873%No
CVE-2026-32183High7.873%No
CVE-2026-33098High7.873%No
CVE-2026-27913High7.773%No
CVE-2026-26154High7.573%No
CVE-2026-32071High7.573%No
CVE-2026-32156High7.473%No
CVE-2026-32149High7.373%No
CVE-2025-64720High7.173%No
CVE-2025-65018High7.173%No
CVE-2026-26151High7.173%No
CVE-2026-26152High7.073%No
CVE-2026-26173High7.073%No
CVE-2026-26174High7.073%No
CVE-2026-26177High7.073%No
CVE-2026-26182High7.073%No
CVE-2026-27908High7.073%No
CVE-2026-27917High7.073%No
CVE-2026-27921High7.073%No
CVE-2026-27922High7.073%No
CVE-2026-27929High7.073%No
CVE-2026-32068High7.073%No
CVE-2026-32070High7.073%No
CVE-2026-32073High7.073%No
CVE-2026-32075High7.073%No
CVE-2026-32080High7.073%No
CVE-2026-32082High7.073%No
CVE-2026-32083High7.073%No
CVE-2026-32086High7.073%No
CVE-2026-32087High7.073%No
CVE-2026-32093High7.073%No
CVE-2026-32150High7.073%No
CVE-2026-33099High7.073%No
CVE-2026-33100High7.073%No
CVE-2026-33104High7.073%No
CVE-2026-0390Medium6.773%No
CVE-2026-26155Medium6.573%No
CVE-2026-27925Medium6.573%No
CVE-2026-32151Medium6.573%No
CVE-2026-32072Medium6.273%No
CVE-2026-26169Medium6.173%No
CVE-2026-25250Medium6.073%No
CVE-2026-23670Medium5.773%No
CVE-2026-27930Medium5.573%No
CVE-2026-32079Medium5.573%No
CVE-2026-32081Medium5.573%No
CVE-2026-32084Medium5.573%No
CVE-2026-32085Medium5.573%No
CVE-2026-32212Medium5.573%No
CVE-2026-32214Medium5.573%No
CVE-2026-32217Medium5.573%No

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

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.