Patch tracker / KB5083768
KB5083768: Windows 10 Version 1809 for 32-bit Sys Security Update (April 2026)
KB5083768 is a Critical security update for Windows 10 Version 1809 for 32-bit Sys, released 2026-04-14. It closes 119 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 119 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.
- Warnings related to Remote Desktop might not display correctly
KB5083768 is an unusually large April 2026 rollup patching 120 CVEs across Windows 11 26H1 (ARM64 and x64) and Windows 10 1809, topping out at Critical severity CVSS 9.8. One of its CVEs is listed in the CISA Known Exploited Vulnerabilities catalog, and the highest EPSS score here is 64 percent, so exploitation risk is measured rather than theoretical. The mix of a brand new 26H1 branch and legacy 1809 in one KB means both cutting edge and long lived deployments are exposed.
Do this: Deploy KB5083768 to all Windows 11 26H1 and Windows 10 1809 systems now, prioritizing internet facing hosts given the KEV listed CVE and the 9.8 Critical entry.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5083768
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5083768
- 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 KB5083768 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5083768 (checked 2026-07-28). Verify against the article before acting.
Warnings related to Remote Desktop 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.
Workaround
This issue is addressed in KB5083806 .
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-20806 | Critical | 9.8 | 56% | No |
| CVE-2026-20928 | Critical | 9.8 | 56% | No |
| CVE-2026-23670 | Critical | 9.8 | 56% | No |
| CVE-2026-25184 | 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-26165 | Critical | 9.8 | 56% | No |
| CVE-2026-26166 | 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-26179 | Critical | 9.8 | 56% | No |
| CVE-2026-26180 | Critical | 9.8 | 56% | No |
| CVE-2026-26181 | 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-27907 | 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-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-32076 | 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-32152 | Critical | 9.8 | 56% | No |
| CVE-2026-32153 | 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-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-32195 | 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-32216 | Critical | 9.8 | 56% | No |
| CVE-2026-32217 | Critical | 9.8 | 56% | No |
| CVE-2026-32218 | Critical | 9.8 | 56% | No |
| CVE-2026-32219 | Critical | 9.8 | 56% | No |
| CVE-2026-32220 | Critical | 9.8 | 56% | No |
| CVE-2026-32221 | Critical | 9.8 | 56% | No |
| CVE-2026-32222 | Critical | 9.8 | 56% | No |
| CVE-2026-32223 | Critical | 9.8 | 56% | No |
| CVE-2026-32224 | Critical | 9.8 | 56% | No |
| CVE-2026-32225 | Critical | 9.8 | 56% | No |
| CVE-2026-33096 | Critical | 9.8 | 56% | No |
| CVE-2026-33098 | Critical | 9.8 | 56% | No |
| CVE-2026-33100 | Critical | 9.8 | 56% | No |
| CVE-2026-33101 | 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
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.