Patch tracker / KB5053603
KB5053603: Windows Server 2019 Security Update (March 2025)
KB5053603 is a High security update for Windows Server 2019, released 2025-03-11. It closes 34 CVEs with a maximum CVSS of 8.8. At least one of them is actively exploited (CISA KEV) and linked to ransomware, so this is a deploy-first update. The most likely of them to be attacked is CVE-2025-24035, which FIRST.org rates at 59% probability of exploitation in the next 30 days.
Update summary
Fixes 34 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 59%. One is linked to ransomware. Among the top 25% of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Windows 10 Version 1809 for 32-bit Systems has shipped since this one: KB5094041 (2026-08-11). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 1 known issue with this update.
- System Gurad Runtime Monitor Broker service
KB5053603 extends March 2025's Windows 10 1809 and Windows Server 2019 fixes to thirty four CVEs, adding CVE-2025-24997 to the CVE-2025-24035 and CVE-2024-9157 set. It carries the same ransomware linkage and CISA KEV listing as its sibling package, with a 59 percent EPSS score, meaning attackers behind extortion operations are actively using at least one of these bugs. Ransomware linked flaws warrant faster turnaround than the CVE count alone might suggest.
Do this: Deploy KB5053603 promptly given its confirmed ransomware association on Windows 10 1809 and Windows Server 2019.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5053603
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5053603
- Released
- 2025-03-11
- Last changed
- 2025-03-11
- Changes tracked
- 1
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 KB5053603 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5053603 (checked 2026-08-11). Verify against the article before acting.
Citrix
Symptom
Workaround
Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024.
Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when restarting the device to complete the update installation, an error message with text similar to “Something didn’t go as planned. No need to worry – undoing changes” appears. The device will then revert to the Windows updates previously present on the device.
This issue likely affects a limited number of organizations as version 2411 of the SRA application is a new version. Home users are not expected to be affected by this issue.
The issue has been resolved in Citrix Session Recording Agent version 2503, released on April 28, 2025, and newer versions.
For details, see the documentation provided by Citrix at " Microsoft's January Security Update Fails/Reverts on a machine with 2411 Session Recording Agent ".
System Gurad Runtime Monitor Broker service
Symptom
Workaround
The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates ...
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-24985 | High | 7.8 | 59% | KEV |
| CVE-2025-24993 | High | 7.8 | 59% | KEV |
| CVE-2025-26633 | High | 7.0 | 59% | KEV Ransomware |
| CVE-2025-24054 | Medium | 6.5 | 59% | KEV |
| CVE-2025-24991 | Medium | 5.5 | 59% | KEV |
| CVE-2025-24984 | Medium | 4.6 | 59% | KEV |
| CVE-2024-9157 | High | 8.8 | 59% | No |
| CVE-2025-21247 | High | 8.8 | 59% | No |
| CVE-2025-24051 | High | 8.8 | 59% | No |
| CVE-2025-24055 | High | 8.8 | 59% | No |
| CVE-2025-24056 | High | 8.8 | 59% | No |
| CVE-2025-24997 | High | 8.8 | 59% | No |
| CVE-2025-26645 | High | 8.8 | 59% | No |
| CVE-2025-24084 | High | 8.4 | 59% | No |
| CVE-2025-24035 | High | 8.1 | 59% | No |
| CVE-2025-24045 | High | 8.1 | 59% | No |
| CVE-2025-24064 | High | 8.1 | 59% | No |
| CVE-2025-21180 | High | 7.8 | 59% | No |
| CVE-2025-24044 | High | 7.8 | 59% | No |
| CVE-2025-24046 | High | 7.8 | 59% | No |
| CVE-2025-24048 | High | 7.8 | 59% | No |
| CVE-2025-24050 | High | 7.8 | 59% | No |
| CVE-2025-24059 | High | 7.8 | 59% | No |
| CVE-2025-24061 | High | 7.8 | 59% | No |
| CVE-2025-24066 | High | 7.8 | 59% | No |
| CVE-2025-24067 | High | 7.8 | 59% | No |
| CVE-2025-24072 | High | 7.8 | 59% | No |
| CVE-2025-24995 | High | 7.8 | 59% | No |
| CVE-2025-25008 | High | 7.1 | 59% | No |
| CVE-2025-24987 | Medium | 6.6 | 59% | No |
| CVE-2025-24988 | Medium | 6.6 | 59% | No |
| CVE-2025-24071 | Medium | 6.5 | 59% | No |
| CVE-2025-24996 | Medium | 6.5 | 59% | No |
| CVE-2025-24992 | Medium | 5.5 | 59% | No |
Scope and sources
- Affected products
- Also released in March 2025
KB5051974
32 CVEs · High · exploitedKB5051979
34 CVEs · High · exploitedKB5051980
34 CVEs · High · exploitedKB5051987
38 CVEs · High · exploitedKB5051989
32 CVEs · High · exploitedKB5052000
34 CVEs · High · exploitedKB5052006
33 CVEs · High · exploitedKB5052040
27 CVEs · High · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.