Patch tracker / KB5073724
KB5073724: Windows 10 Version 1809 for 32-bit Sys Security Update (January 2026)
Updated July 21, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva provides Three Free Unlimited Audits, including all tenants and full Claude MCP.Start my Audit
Microsoft security update released 2026-01-13. Fixes 73 CVEs.
All about KB5073724: the download, the Senserva AI read, a PowerShell installed-check, install guidance, the CVEs it fixes, and its change history.
KB5073724 is a Critical security update for Windows 10 Version 1809 for 32-bit Sys, released 2026-01-13. It closes 73 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. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.
Exploitation is not theoretical here: at least one CVE this update fixes is on the CISA Known Exploited Vulnerabilities catalog, which means attackers are already using it against unpatched systems. For an update like this, the risk window is the gap between today and the day your last device installs it, so shortening that gap matters more than perfect scheduling.
Most organizations deliver an update like this automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; the install section below covers each path, including how to expedite it for the exploited CVE. For the bigger picture: how the Microsoft patching tools fit together, this month's Patch Tuesday summary, and every update ranked by real-world risk.
Download KB5073724
Get the official update for KB5073724. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5073724
KB5073724 is a large January 2026 rollup fixing 73 CVEs across Windows 11 25H2 (x64 and ARM64) and the older Windows 10 1809, with a Critical flaw rated CVSS 9.8 and an EPSS of 73 percent. One of the included CVEs is on the CISA KEV list, meaning it is confirmed exploited in the wild, though none are currently tied to ransomware campaigns. The mix of a bleeding-edge 25H2 branch and legacy 1809 in the same KB means both your newest and oldest supported machines need this.
Do this: Prioritize deploying KB5073724 first to internet-facing and 1809 systems given the confirmed KEV-listed CVE and the 9.8 Critical flaw.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5073724
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5073724
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.
Exploitation and severity
Fixes 73 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 73%.
Among the top 10% of tracked Microsoft updates by EPSS exploit probability.
What to do
Treat as urgent: it is being exploited in the wild (CISA KEV), so patch ahead of items that are not. Senserva flags whether KB5073724 is missing on your devices.
Check if KB5073724 is installed
Copy-paste PowerShell: one machine, or your whole fleet in one pass. No output means the update is not installed.
Get-HotFix covers Windows updates. Office, SharePoint, and Exchange server updates show under installed updates in Programs and Features, or check the Update Catalog history.
Writing about KB5073724? Cite this page
Copy-paste for a blog post, forum answer, or internal doc. The link always carries the current risk data.
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-2026-20805 | Critical | 9.8 | 73% | KEV |
| CVE-2023-31096 | Critical | 9.8 | 73% | No |
| CVE-2024-55414 | Critical | 9.8 | 73% | No |
| CVE-2025-6965 | Critical | 9.8 | 73% | No |
| CVE-2026-20804 | Critical | 9.8 | 73% | No |
| CVE-2026-20809 | Critical | 9.8 | 73% | No |
| CVE-2026-20810 | Critical | 9.8 | 73% | No |
| CVE-2026-20812 | Critical | 9.8 | 73% | No |
| CVE-2026-20814 | Critical | 9.8 | 73% | No |
| CVE-2026-20816 | Critical | 9.8 | 73% | No |
| CVE-2026-20817 | Critical | 9.8 | 73% | No |
| CVE-2026-20820 | Critical | 9.8 | 73% | No |
| CVE-2026-20821 | Critical | 9.8 | 73% | No |
| CVE-2026-20822 | Critical | 9.8 | 73% | No |
| CVE-2026-20823 | Critical | 9.8 | 73% | No |
| CVE-2026-20824 | Critical | 9.8 | 73% | No |
| CVE-2026-20825 | Critical | 9.8 | 73% | No |
| CVE-2026-20826 | Critical | 9.8 | 73% | No |
| CVE-2026-20827 | Critical | 9.8 | 73% | No |
| CVE-2026-20828 | Critical | 9.8 | 73% | No |
| CVE-2026-20829 | Critical | 9.8 | 73% | No |
| CVE-2026-20831 | Critical | 9.8 | 73% | No |
| CVE-2026-20832 | Critical | 9.8 | 73% | No |
| CVE-2026-20834 | Critical | 9.8 | 73% | No |
| CVE-2026-20836 | Critical | 9.8 | 73% | No |
| CVE-2026-20837 | Critical | 9.8 | 73% | No |
| CVE-2026-20839 | Critical | 9.8 | 73% | No |
| CVE-2026-20840 | Critical | 9.8 | 73% | No |
| CVE-2026-20842 | Critical | 9.8 | 73% | No |
| CVE-2026-20843 | Critical | 9.8 | 73% | No |
| CVE-2026-20844 | Critical | 9.8 | 73% | No |
| CVE-2026-20847 | Critical | 9.8 | 73% | No |
| CVE-2026-20848 | Critical | 9.8 | 73% | No |
| CVE-2026-20849 | Critical | 9.8 | 73% | No |
| CVE-2026-20852 | Critical | 9.8 | 73% | No |
| CVE-2026-20853 | Critical | 9.8 | 73% | No |
| CVE-2026-20856 | Critical | 9.8 | 73% | No |
| CVE-2026-20857 | Critical | 9.8 | 73% | No |
| CVE-2026-20858 | Critical | 9.8 | 73% | No |
| CVE-2026-20860 | Critical | 9.8 | 73% | No |
| CVE-2026-20861 | Critical | 9.8 | 73% | No |
| CVE-2026-20862 | Critical | 9.8 | 73% | No |
| CVE-2026-20864 | Critical | 9.8 | 73% | No |
| CVE-2026-20865 | Critical | 9.8 | 73% | No |
| CVE-2026-20866 | Critical | 9.8 | 73% | No |
| CVE-2026-20867 | Critical | 9.8 | 73% | No |
| CVE-2026-20868 | Critical | 9.8 | 73% | No |
| CVE-2026-20869 | Critical | 9.8 | 73% | No |
| CVE-2026-20871 | Critical | 9.8 | 73% | No |
| CVE-2026-20872 | Critical | 9.8 | 73% | No |
| CVE-2026-20873 | Critical | 9.8 | 73% | No |
| CVE-2026-20874 | Critical | 9.8 | 73% | No |
| CVE-2026-20875 | Critical | 9.8 | 73% | No |
| CVE-2026-20877 | Critical | 9.8 | 73% | No |
| CVE-2026-20918 | Critical | 9.8 | 73% | No |
| CVE-2026-20919 | Critical | 9.8 | 73% | No |
| CVE-2026-20921 | Critical | 9.8 | 73% | No |
| CVE-2026-20922 | Critical | 9.8 | 73% | No |
| CVE-2026-20923 | Critical | 9.8 | 73% | No |
| CVE-2026-20924 | Critical | 9.8 | 73% | No |
| CVE-2026-20925 | Critical | 9.8 | 73% | No |
| CVE-2026-20926 | Critical | 9.8 | 73% | No |
| CVE-2026-20927 | Critical | 9.8 | 73% | No |
| CVE-2026-20929 | Critical | 9.8 | 73% | No |
| CVE-2026-20931 | Critical | 9.8 | 73% | No |
| CVE-2026-20932 | Critical | 9.8 | 73% | No |
| CVE-2026-20934 | Critical | 9.8 | 73% | No |
| CVE-2026-20936 | Critical | 9.8 | 73% | No |
| CVE-2026-20937 | Critical | 9.8 | 73% | No |
| CVE-2026-20939 | Critical | 9.8 | 73% | No |
| CVE-2026-20940 | Critical | 9.8 | 73% | No |
| CVE-2026-20962 | Critical | 9.8 | 73% | No |
| CVE-2026-21265 | Critical | 9.8 | 73% | No |
Affected products
Also released in January 2026
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5073724
Any of these paths delivers KB5073724; most organizations already have one of the first three running:
- Intune update rings (Windows Update for Business): the update flows on each ring's deferral schedule. For this update, consider an expedite policy: it bypasses deferrals for exactly this fix-now case.
- Windows Autopatch: rings, rollout, and pause or rollback are managed for you; exploited updates can be expedited.
- WSUS / Configuration Manager: approve KB5073724 for your device groups and set a deadline (deadline, not just approval, for an exploited fix).
- Manual: download from the Update Catalog above and install; fine for a handful of machines, unmanageable at any real scale.
After the rollout, verify rather than assume: update compliance reporting in Intune or Autopatch shows which devices actually installed it, and Siemserva reads Intune, Defender, Autopatch, and Azure Update Manager together to show the devices still missing KB5073724, ranked by exploitation.
Common questions about KB5073724
Is KB5073724 urgent?
Yes. KB5073724 fixes at least one vulnerability in the CISA Known Exploited Vulnerabilities catalog, meaning attackers are using it in the wild. Deploy it first.
How do I download KB5073724?
From the Microsoft Update Catalog (linked on this page), or let Intune, Windows Update for Business, Windows Autopatch, or WSUS deliver it. The catalog page lists the download for each supported product.
How do I deploy KB5073724 with Intune?
Assign a Windows Update ring (quality update policy) to the device groups and the update flows on the ring's deferral schedule. Because KB5073724 fixes an actively exploited CVE, an Intune expedite policy is the right tool: it bypasses configured deferrals and pushes the update as soon as devices check in. Verify the rollout with update compliance reporting rather than assuming delivery.
Can I ask my own AI about KB5073724?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5073724's key facts: severity, CVE count, exploitation status, and the download link. Copy it into Claude, ChatGPT, or Copilot for a rollout plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.
