Patch tracker / CVE reference / CVE-2025-49673
CVE-2025-49673
CVE-2025-49673 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Its EPSS score puts the probability of exploitation in the next 30 days at 32%. Microsoft has shipped the fix: deploy one of the 11 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Not in the CISA KEV catalog. EPSS exploit probability 32%. CVSS 8.8 (High).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
Rated Critical at CVSS 9.8 with a 22% EPSS score, this RRAS remote code execution flaw affects the same Windows Server 2019 and 2022 footprint as its many siblings. One cumulative update resolves the whole family, which simplifies the response considerably.
Do this: Deploy the cumulative update to all Remote Access role holders and record the RRAS host list for faster response next time.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-49673
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2025-49673
Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5062553, KB5062557, KB5062560, KB5062570, KB5062572, KB5062592, KB5062597, KB5062618, KB5062619, KB5062624, KB5062632 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-49673. 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.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.