Patch tracker / KB5063877
KB5063877: Windows Server 2019 Security Update (August 2025)
KB5063877 is a Critical security update for Windows Server 2019, released 2025-08-12. It closes 54 CVEs with a maximum CVSS of 9.8. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.
Microsoft security update released 2025-08-12. Fixes 54 CVEs.
No exploitation is confirmed yet, but the EPSS model puts the 30-day exploitation probability for the worst CVE here at 38%, which is high enough to treat this as more urgent than its Critical label alone suggests. Attackers reverse-engineer Patch Tuesday updates within days, so the safe assumption is that exploit code follows the patch.
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. 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.
Updated July 24, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Download KB5063877
Get the official update for KB5063877. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5063877
KB5063877 is the August 12, 2025 rollup for Windows 10 1809 and Windows Server 2019, closing 54 CVEs including one rated Critical at CVSS 9.8. The top EPSS across this set is 38 percent and none are listed in the CISA KEV catalog or tied to ransomware, so this is a large but not yet actively exploited batch. The exposure is broad because Server 2019 including Core installations covers many domain-joined and infrastructure roles.
Do this: Approve KB5063877 for your Windows Server 2019 and Windows 10 1809 rings and stage it to Server Core hosts, prioritizing internet-facing and domain infrastructure servers first.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5063877
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5063877
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 54 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 38%.
Among the top 25% of tracked Microsoft updates by EPSS exploit probability.
What to do
Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. Senserva flags whether KB5063877 is missing on your devices.
Check if KB5063877 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 KB5063877? 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-2025-49743 | Critical | 9.8 | 38% | No |
| CVE-2025-49751 | Critical | 9.8 | 38% | No |
| CVE-2025-49761 | Critical | 9.8 | 38% | No |
| CVE-2025-49762 | Critical | 9.8 | 38% | No |
| CVE-2025-50153 | Critical | 9.8 | 38% | No |
| CVE-2025-50154 | Critical | 9.8 | 38% | No |
| CVE-2025-50155 | Critical | 9.8 | 38% | No |
| CVE-2025-50156 | Critical | 9.8 | 38% | No |
| CVE-2025-50157 | Critical | 9.8 | 38% | No |
| CVE-2025-50158 | Critical | 9.8 | 38% | No |
| CVE-2025-50159 | Critical | 9.8 | 38% | No |
| CVE-2025-50160 | Critical | 9.8 | 38% | No |
| CVE-2025-50161 | Critical | 9.8 | 38% | No |
| CVE-2025-50162 | Critical | 9.8 | 38% | No |
| CVE-2025-50163 | Critical | 9.8 | 38% | No |
| CVE-2025-50164 | Critical | 9.8 | 38% | No |
| CVE-2025-50166 | Critical | 9.8 | 38% | No |
| CVE-2025-50167 | Critical | 9.8 | 38% | No |
| CVE-2025-50170 | Critical | 9.8 | 38% | No |
| CVE-2025-50172 | Critical | 9.8 | 38% | No |
| CVE-2025-50173 | Critical | 9.8 | 38% | No |
| CVE-2025-50177 | Critical | 9.8 | 38% | No |
| CVE-2025-53131 | Critical | 9.8 | 38% | No |
| CVE-2025-53132 | Critical | 9.8 | 38% | No |
| CVE-2025-53134 | Critical | 9.8 | 38% | No |
| CVE-2025-53135 | Critical | 9.8 | 38% | No |
| CVE-2025-53136 | Critical | 9.8 | 38% | No |
| CVE-2025-53137 | Critical | 9.8 | 38% | No |
| CVE-2025-53138 | Critical | 9.8 | 38% | No |
| CVE-2025-53140 | Critical | 9.8 | 38% | No |
| CVE-2025-53141 | Critical | 9.8 | 38% | No |
| CVE-2025-53143 | Critical | 9.8 | 38% | No |
| CVE-2025-53144 | Critical | 9.8 | 38% | No |
| CVE-2025-53145 | Critical | 9.8 | 38% | No |
| CVE-2025-53147 | Critical | 9.8 | 38% | No |
| CVE-2025-53148 | Critical | 9.8 | 38% | No |
| CVE-2025-53149 | Critical | 9.8 | 38% | No |
| CVE-2025-53151 | Critical | 9.8 | 38% | No |
| CVE-2025-53152 | Critical | 9.8 | 38% | No |
| CVE-2025-53153 | Critical | 9.8 | 38% | No |
| CVE-2025-53154 | Critical | 9.8 | 38% | No |
| CVE-2025-53155 | Critical | 9.8 | 38% | No |
| CVE-2025-53716 | Critical | 9.8 | 38% | No |
| CVE-2025-53718 | Critical | 9.8 | 38% | No |
| CVE-2025-53719 | Critical | 9.8 | 38% | No |
| CVE-2025-53720 | Critical | 9.8 | 38% | No |
| CVE-2025-53721 | Critical | 9.8 | 38% | No |
| CVE-2025-53722 | Critical | 9.8 | 38% | No |
| CVE-2025-53723 | Critical | 9.8 | 38% | No |
| CVE-2025-53724 | Critical | 9.8 | 38% | No |
| CVE-2025-53725 | Critical | 9.8 | 38% | No |
| CVE-2025-53726 | Critical | 9.8 | 38% | No |
| CVE-2025-53766 | Critical | 9.8 | 38% | No |
| CVE-2025-53778 | Critical | 9.8 | 38% | No |
Affected products
Also released in August 2025
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5063877
Any of these paths delivers KB5063877; 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.
- Windows Autopatch: rings, rollout, and pause or rollback are managed for you; exploited updates can be expedited.
- WSUS / Configuration Manager: approve KB5063877 for your device groups and set a deadline.
- 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 KB5063877, ranked by exploitation.
Common questions about KB5063877
Is KB5063877 urgent?
KB5063877 is rated Critical with a maximum CVSS of 9.8. No active exploitation is confirmed yet, so schedule it in your prompt patch cycle.
How do I download KB5063877?
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 KB5063877 with Intune?
Assign a Windows Update ring (quality update policy) to the device groups and the update flows on the ring's deferral schedule. For urgent updates, Intune expedite policies can bypass the ring deferrals. Verify the rollout with update compliance reporting rather than assuming delivery.
Can I ask my own AI about KB5063877?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5063877'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.
