Patch tracker / CVE reference / CVE-2025-21172

CVE-2025-21172

CVE-2025-21172 is a high severity Microsoft vulnerability with a CVSS score of 7.5. Microsoft has shipped the fix: deploy one of the 3 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.5

CVSS

2.4%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.4%. CVSS 7.5 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2025-21172

This is a .NET and Visual Studio remote code execution bug rated High 8.8, and notably its EPSS sits at just 2 percent, far below the network-facing Windows flaws in this batch. It affects developer toolchains: Visual Studio 2017 15.9, 2019 16.11, and 2022 17.6. Exploitation typically requires a developer to open or build a malicious project, so the risk concentrates on build machines and workstations rather than servers.

Do this: Update Visual Studio 2017, 2019, and 2022 on developer and CI build machines, and caution engineers against opening untrusted solutions.

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

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

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-21172 (source: https://senserva.com/cve/CVE-2025-21172.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-21172: High severity Microsoft vulnerability, CVSS 7.5
- EPSS 30-day exploitation probability: 2.4%
- Actively exploited (CISA KEV): no
- Fixed by: KB5049688, KB5050525, KB5050526
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.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 2%.

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

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2025-21172

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5049688, KB5050525, KB5050526 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-21172. 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.

KB5049688 KB5050525 KB5050526

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-21176 CVE-2025-21178 CVE-2025-21171 CVE-2025-21173

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.