Patch tracker / KB5053995

KB5053995: Windows Server 2019 Security Update (March 2025)

KB5053995 is a High security update for Windows Server 2019, released 2025-03-11. It closes 19 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

HighCISA KEVRansomware
2025-03-11
Released
19
CVEs fixed
8.8
Max CVSS
High
Severity
Deploy immediately
This update fixes vulnerabilities confirmed exploited in the wild, including ransomware-linked CVEs.

Fixes 19 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 30%. One is linked to ransomware. Among the top 25% of tracked Microsoft updates by EPSS exploit probability.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

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.

Senserva found thisread these before you deploy broadly

Microsoft documents 1 known issue with this update.

  • |

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5053995Microsoft support article
Senserva AI Opinion for KB5053995

KB5053995 is the counterpart March 2025 update for the same Windows 10 1809 and Server 2019 population, fixing the identical 19-CVE set as KB5053888, including the ransomware-linked, CISA-KEV-listed flaws and the 32 percent EPSS score. Having two KBs for the same servicing branch this month usually means different update channels reaching the same machines, so admins need to make sure one of the two actually gets installed. Skipping both leaves the ransomware-associated exposure open.

Do this: Verify which of KB5053888 or KB5053995 your deployment ring received, and reconcile so no Windows 10 1809 or Server 2019 host is left on neither.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for KB5053995

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for KB5053995

Released
2025-03-11
Last changed
2026-08-07
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 KB5053995 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5053995 (checked 2026-08-11). Verify against the article before acting.

|

| Symptom

| Next step

| After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History .

| This is expected in the following circumstances:

If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181 .

If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.

For the most up-to-date information about known issues for Windows Server 2008 SP2, 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.

CVESeverityCVSSEPSSExploited
CVE-2025-24985High7.859%KEV
CVE-2025-24993High7.859%KEV
CVE-2025-24983High7.059%KEV
CVE-2025-26633High7.059%KEV Ransomware
CVE-2025-24991Medium5.559%KEV
CVE-2024-9157High8.859%No
CVE-2025-21247High8.859%No
CVE-2025-24051High8.859%No
CVE-2025-24055High8.859%No
CVE-2025-24056High8.859%No
CVE-2025-26645High8.859%No
CVE-2025-24035High8.159%No
CVE-2025-24064High8.159%No
CVE-2025-21180High7.859%No
CVE-2025-24059High7.859%No
CVE-2025-24072High7.859%No
CVE-2025-24987Medium6.659%No
CVE-2025-24988Medium6.659%No
CVE-2025-24992Medium5.559%No

Scope and sources

Affected products
Also released in March 2025

KB5051974

32 CVEs · High · exploited

KB5051979

34 CVEs · High · exploited

KB5051980

34 CVEs · High · exploited

KB5051987

38 CVEs · High · exploited

KB5051989

32 CVEs · High · exploited

KB5052000

34 CVEs · High · exploited

KB5052006

33 CVEs · High · exploited

KB5052040

27 CVEs · High · exploited

The full month, summarized: Microsoft Patch Tuesday.

Authoritative references
Official KB5053995 page (Microsoft Support)Microsoft Update CatalogMicrosoft Security Update Guide

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.