Patch tracker / KB5082198
KB5082198: Windows 10 Version 1809 for 32-bit Sys Security Update (April 2026)
KB5082198 is a Critical security update for Windows 10 Version 1809 for 32-bit Sys, released 2026-04-14. It closes 87 CVEs with a maximum CVSS of 9.8. The most likely of them to be attacked is CVE-2026-25250, which FIRST.org rates at 56% probability of exploitation in the next 30 days.
Update summary
Fixes 87 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.
Microsoft documents 1 known issue with this update.
- Domain controllers might restart repeatedly after installing this update
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-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 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-07-28). 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.
| 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-20928 | 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-26154 | 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-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-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-26183 | 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-27912 | Critical | 9.8 | 56% | No |
| CVE-2026-27913 | 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-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-27925 | Critical | 9.8 | 56% | No |
| CVE-2026-27928 | Critical | 9.8 | 56% | No |
| CVE-2026-27929 | Critical | 9.8 | 56% | No |
| CVE-2026-27930 | Critical | 9.8 | 56% | No |
| CVE-2026-32068 | 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-32075 | Critical | 9.8 | 56% | No |
| CVE-2026-32077 | Critical | 9.8 | 56% | No |
| CVE-2026-32079 | Critical | 9.8 | 56% | No |
| CVE-2026-32080 | 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-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-32154 | Critical | 9.8 | 56% | No |
| CVE-2026-32156 | Critical | 9.8 | 56% | No |
| CVE-2026-32157 | Critical | 9.8 | 56% | No |
| CVE-2026-32164 | 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-32217 | 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-33826 | 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
KB5002853
2 CVEs · Medium · exploitedKB5002854
2 CVEs · Medium · exploitedKB5002861
2 CVEs · Medium · exploitedKB5082052
115 CVEs · CriticalKB5082060
121 CVEs · CriticalKB5082063
124 CVEs · CriticalKB5082123
107 CVEs · CriticalKB5082142
116 CVEs · CriticalThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.