Patch tracker / CVE reference / CVE-2025-21219

CVE-2025-21219

CVE-2025-21219 is a critical severity Microsoft vulnerability with a CVSS score of 9.8. Its EPSS score puts the probability of exploitation in the next 30 days at 81%. Microsoft has shipped the fix: deploy one of the 8 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Critical

9.8

CVSS

81%

EPSS, 30 days

Critical

Severity

Not in the CISA KEV catalog. EPSS exploit probability 81%. CVSS 9.8 (Critical).

This CVE is among the top 10% of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2025-21219

Yet another MapUrlToZone security feature bypass, Critical at CVSS 9.8 and 81 percent EPSS, affects Windows 10 Version 1809 (32-bit and x64) and Windows Server 2019. With several MapUrlToZone bypasses landing in the same window at this severity and probability, admins should confirm every one of them is applied rather than assuming one update covers the class.

Do this: Verify this specific MapUrlToZone CVE is closed on Windows 10 1809 and Server 2019, not just one of the other related bypasses.

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

Senserva AI Opinion and rich prompt for CVE-2025-21219

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

I am an IT admin assessing a vulnerability. Facts for CVE-2025-21219 (source: https://senserva.com/cve/CVE-2025-21219.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-21219: Critical severity Microsoft vulnerability, CVSS 9.8
- EPSS 30-day exploitation probability: 81%
- Actively exploited (CISA KEV): no
- Fixed by: KB5049981, KB5049983, KB5049984, KB5049993, KB5050008, KB5050009, KB5050013, KB5050021
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 81%).

Fixed by KB5049981 and 7 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2025-21219

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5049981, KB5049983, KB5049984, KB5049993, KB5050008, KB5050009, KB5050013, KB5050021 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2025-21219. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5049981 KB5049983 KB5049984 KB5049993 KB5050008 KB5050009 KB5050013 KB5050021

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-21333 CVE-2025-21334 CVE-2025-21335 CVE-2025-21189 CVE-2025-21210 CVE-2025-21214 CVE-2025-21268 CVE-2025-21269

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.