Patch tracker / KB5055547

KB5055547: Windows Server 2019 Security Update (April 2025)

KB5055547 is a High security update for Windows Server 2019, released 2025-04-08. It closes 43 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-26663, which FIRST.org rates at 14% probability of exploitation in the next 30 days.

Update summary

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

Fixes 43 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 14%. One is linked to ransomware. Among the top half 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.

  • Microsoft is not currently aware of any issues with this update.

The full text, quoted from Microsoft

Senserva AI Opinion for KB5055547

KB5055547 is a smaller April 2025 package at 45 CVEs for Windows 10 1809 and Windows Server 2019, still High severity, CVSS 8.8, 18 percent EPSS, carrying the same CISA KEV listing and ransomware linkage as the rest of this month's family. Smaller CVE count here likely means a narrower servicing branch, not a lower-risk one, since the ransomware association applies to the shared core CVEs it still contains. Verify it against a broader sibling before assuming completeness.

Do this: Confirm KB5055547 closes the ransomware-linked CVEs shared with the larger April 2025 builds before treating any host running it as fully remediated.

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

Senserva AI Opinion and rich prompt for KB5055547

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

Full tracking and change history for KB5055547

Released
2025-04-08
Last changed
2026-08-12
Changes tracked
4

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.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is the single recorded change on 2026-08-07, when the CVE count for KB5055547 dropped from 45 to 43. This is a downward move, meaning two fewer CVEs are now associated with this update. For an admin today, the trail is short and stable with no further activity, so treat the current figure of 43 as the working baseline.

  • 2026-08-07 CVEs fixed 45 to 43

Recorded by Senserva on the dates shown, from the MSRC release feed. This is what moved and when, which neither the vendor advisory nor NVD publishes.

Check if KB5055547 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

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

Microsoft is not currently aware of any issues with this update.

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-29824High7.814%KEV Ransomware
CVE-2025-21205High8.814%No
CVE-2025-21221High8.814%No
CVE-2025-21222High8.814%No
CVE-2025-26669High8.814%No
CVE-2025-27477High8.814%No
CVE-2025-27481High8.814%No
CVE-2025-27737High8.614%No
CVE-2025-26663High8.114%No
CVE-2025-26670High8.114%No
CVE-2025-27487High8.014%No
CVE-2025-21204High7.814%No
CVE-2025-24073High7.814%No
CVE-2025-26648High7.814%No
CVE-2025-26679High7.814%No
CVE-2025-26688High7.814%No
CVE-2025-27483High7.814%No
CVE-2025-27727High7.814%No
CVE-2025-27733High7.814%No
CVE-2025-27741High7.814%No
CVE-2025-26641High7.514%No
CVE-2025-26668High7.514%No
CVE-2025-26673High7.514%No
CVE-2025-26686High7.514%No
CVE-2025-26687High7.514%No
CVE-2025-27469High7.514%No
CVE-2025-27473High7.514%No
CVE-2025-27484High7.514%No
CVE-2025-29810High7.514%No
CVE-2025-27491High7.114%No
CVE-2025-29809High7.114%No
CVE-2025-21191High7.014%No
CVE-2025-26665High7.014%No
CVE-2025-27478High7.014%No
CVE-2025-27732High7.014%No
CVE-2025-26637Medium6.814%No
CVE-2025-21197Medium6.514%No
CVE-2025-26672Medium6.514%No
CVE-2025-27738Medium6.514%No
CVE-2025-27735Medium6.014%No
CVE-2025-27471Medium5.914%No
CVE-2025-27742Medium5.514%No
CVE-2025-27472Medium5.414%No

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.