Patch tracker / CVE reference / CVE-2025-21176

CVE-2025-21176

CVE-2025-21176 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 81%. Microsoft has shipped the fix: deploy one of the 19 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.8

CVSS

81%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 81%. CVSS 8.8 (High).

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

Senserva AI Opinion for CVE-2025-21176

.NET, .NET Framework, and Visual Studio share this remote code execution flaw, rated Critical at CVSS 9.8 with an 81% EPSS score. Visual Studio 2017 15.9, 2019 16.11, and 2022 17.6 are listed, which puts developer machines and build servers squarely in scope, and compromised build infrastructure threatens everything it produces.

Do this: Update Visual Studio and .NET runtimes on build agents and developer workstations first, treating CI servers as the highest-value targets.

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

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

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-21176 (source: https://senserva.com/cve/CVE-2025-21176.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-21176: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 81%
- Actively exploited (CISA KEV): no
- Fixed by: KB5049614, KB5049620, KB5049622, KB5049624, KB5049688, KB5049993, KB5050013, KB5050180, KB5050181, KB5050182, KB5050183, KB5050184, KB5050185, KB5050186, KB5050187, KB5050188, KB5050416, 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.

Patch this cycle

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

Fixed by KB5049614 and 18 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-21176

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5049614, KB5049620, KB5049622, KB5049624, KB5049688, KB5049993, KB5050013, KB5050180, KB5050181, KB5050182, KB5050183, KB5050184, KB5050185, KB5050186, KB5050187, KB5050188, KB5050416, 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-21176. 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.

KB5049614 KB5049620 KB5049622 KB5049624 KB5049688 KB5049993 KB5050013 KB5050180 KB5050181 KB5050182 KB5050183 KB5050184 KB5050185 KB5050186 KB5050187 KB5050188 KB5050416 KB5050525 KB5050526

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

CVE-2025-21176

Risk summary

Official patch(es) for CVE-2025-21176

Scope and sources