Patch tracker / KB5082127
KB5082127: Windows 10 Version 1809 for 32-bit Sys Security Update (April 2026)
KB5082127 is a High security update for Windows 10 Version 1809 for 32-bit Sys, released 2026-04-14. It closes 58 CVEs with a maximum CVSS of 8.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 58 CVEs. Most severe CVSS 8.8 (High). EPSS exploit probability up to 3.5%. Among the top half of tracked Microsoft updates by EPSS exploit probability.
Microsoft documents 1 known issue with this update.
- We are currently not aware of any issues with this update. For the most up-to-date information about known issues for Windows Server 2012, please go...
KB5082127 patches 59 CVEs across Windows 11 26H1 (ARM64 and x64) and Windows 10 1809, with a top severity of High at CVSS 8.8 and one CVE already listed in CISA KEV, meaning it is confirmed exploited in the wild. The 64 percent EPSS on the worst issue signals a high probability of near-term exploitation activity, though none of these CVEs are tied to known ransomware campaigns. The mix of a legacy 1809 build alongside the newest 26H1 release means both older and current fleets need this same rollup.
Do this: Prioritize deploying KB5082127 to internet-facing and 1809 systems first given the CISA KEV listing and 64 percent EPSS, then complete the rest of the fleet within your normal patch window.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5082127
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5082127
- 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 KB5082127 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5082127 (checked 2026-07-22). Verify against the article before acting.
We are currently not aware of any issues with this update. For the most up-to-date information about known issues for Windows Server 2012, please go to the Windows release health dashboard .
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-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-26159 | Critical | 9.8 | 56% | No |
| CVE-2026-26160 | Critical | 9.8 | 56% | No |
| CVE-2026-26162 | Critical | 9.8 | 56% | No |
| CVE-2026-26168 | Critical | 9.8 | 56% | No |
| CVE-2026-26173 | Critical | 9.8 | 56% | No |
| CVE-2026-26174 | Critical | 9.8 | 56% | No |
| CVE-2026-26176 | Critical | 9.8 | 56% | No |
| CVE-2026-26177 | 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-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-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-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-32073 | Critical | 9.8 | 56% | No |
| CVE-2026-32075 | Critical | 9.8 | 56% | No |
| CVE-2026-32077 | 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-32086 | Critical | 9.8 | 56% | No |
| CVE-2026-32087 | Critical | 9.8 | 56% | No |
| CVE-2026-32093 | Critical | 9.8 | 56% | No |
| CVE-2026-32150 | Critical | 9.8 | 56% | No |
| CVE-2026-32151 | Critical | 9.8 | 56% | No |
| CVE-2026-32156 | Critical | 9.8 | 56% | No |
| CVE-2026-32157 | 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-33099 | Critical | 9.8 | 56% | No |
| CVE-2026-33100 | Critical | 9.8 | 56% | No |
| CVE-2026-33104 | 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.