Patch tracker / KB5052032

KB5052032: Windows Server 2008 R2 Security Update (February 2025)

KB5052032 is a High security update for Windows Server 2008 R2, released 2025-02-11. It closes 20 CVEs with a maximum CVSS of 8.8. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. The most likely of them to be attacked is CVE-2025-21352, which FIRST.org rates at 40% probability of exploitation in the next 30 days.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Update summary

HighCISA KEV

2025-02-11

Released

CVEs fixed

8.8

Max CVSS v3

High

Severity

Deploy now

This update fixes vulnerabilities confirmed exploited in the wild.

Fixes 20 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 9.4%. 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 Server 2008 R2 for x64-based Systems Service Pack 1 has shipped since this one: KB5073695 (2026-01-13). 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 Update Catalog: download KB5052032 Microsoft support article

Senserva AI Opinion for KB5052032

KB5052032 adds CVE-2025-21419 to KB5052072's February 2025 fix list, bringing the total to 20 CVEs for Windows 10 1809 and Windows Server 2019, with the same High, CVSS 8.8 severity, 9 percent EPSS, and CISA KEV entry. As with its sibling, don't let the modest EPSS score suggest this can wait; a KEV listing means exploitation is already confirmed, independent of that predictive score. Confirm the extra CVE is relevant to your environment before choosing between the two builds.

Do this: Choose KB5052032 over KB5052072 where CVE-2025-21419 applies to your environment, and deploy either promptly given the CISA KEV listing.

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

Senserva AI Opinion and rich prompt for KB5052032

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

I am an IT admin triaging Microsoft updates. Facts for KB5052032 (source: https://senserva.com/kb/5052032.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- Update: KB5052032, Windows Server 2008 R2, released 2025-02-11
- Severity: High; fixes 20 CVEs, max CVSS 8.8
- Actively exploited (CISA KEV): YES
- CVEs include: CVE-2025-21181, CVE-2025-21190, CVE-2025-21200, CVE-2025-21201, CVE-2025-21208, CVE-2025-21337, CVE-2025-21350, CVE-2025-21352 and 12 more
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5052032
Using only these facts plus your general knowledge, tell me: 1) How urgent this update is and why, in two sentences. 2) Which systems should get it first. 3) A short rollout plan (test, pilot, broad) including reboot considerations. 4) What to verify after deployment.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for KB5052032

Released: 2025-02-11
Last changed: 2026-09-26
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 KB5052032 is installed

Elevated PowerShell. No output means it is not installed.

# Is KB5052032 installed? (elevated PowerShell)
Get-HotFix -Id KB5052032 -ErrorAction SilentlyContinue

# Across many machines (replace the names):
Invoke-Command -ComputerName SERVER01,SERVER02 {
  Get-HotFix -Id KB5052032 -ErrorAction SilentlyContinue
} | Select-Object PSComputerName, HotFixID, InstalledOn

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-21418	High	7.8	40%	KEV
CVE-2025-21190	High	8.8	40%	No
CVE-2025-21200	High	8.8	40%	No
CVE-2025-21201	High	8.8	40%	No
CVE-2025-21208	High	8.8	40%	No
CVE-2025-21368	High	8.8	40%	No
CVE-2025-21369	High	8.8	40%	No
CVE-2025-21371	High	8.8	40%	No
CVE-2025-21406	High	8.8	40%	No
CVE-2025-21407	High	8.8	40%	No
CVE-2025-21410	High	8.8	40%	No
CVE-2025-21376	High	8.1	40%	No
CVE-2025-21359	High	7.8	40%	No
CVE-2025-21373	High	7.8	40%	No
CVE-2025-21375	High	7.8	40%	No
CVE-2025-21181	High	7.5	40%	No
CVE-2025-21419	High	7.1	40%	No
CVE-2025-21352	Medium	6.5	40%	No
CVE-2025-21350	Medium	5.9	40%	No
CVE-2025-21337	Low	3.3	40%	No

Scope and sources

Affected products

Also released in February 2025

Authoritative references

Official KB5052032 page (Microsoft Support)Microsoft Update Catalog Microsoft Security Update Guide

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

KB5052032: Windows Server 2008 R2 Security Update (February 2025)

Update summary

Full tracking and change history for KB5052032

Check if KB5052032 is installed

CVEs fixed by this update

Scope and sources

KB5051974

KB5051979

KB5051980

KB5051987

KB5051989

KB5052000

KB5052006

KB5052016