Patch tracker / CVE reference / CVE-2025-50169

CVE-2025-50169

CVE-2025-50169 is a high severity Microsoft vulnerability with a CVSS score of 7.5. Its EPSS score puts the probability of exploitation in the next 30 days at 38%. Microsoft has shipped the fix: deploy one of the 2 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

38%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 38%. 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-50169

A remote code execution flaw in Windows SMB rated Critical at CVSS 9.8 with a 36 percent exploit probability, and the affected platforms are current: Windows Server 2025 Server Core and Windows 11 24H2 on both architectures. SMB RCE is the vulnerability class behind the most damaging worms in Windows history, and this one lives in your newest builds rather than legacy stragglers. A 36 percent EPSS on an SMB code execution bug deserves out-of-cycle attention.

Do this: Patch Windows Server 2025 and Windows 11 24H2 systems now and double-check that port 445 is not exposed to the internet anywhere.

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

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

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

Fixed by KB5063878 and 1 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-50169

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 KB5063878, KB5064010 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-50169. 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.

KB5063878 KB5064010

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-50165 CVE-2025-53766 CVE-2025-50171 CVE-2025-50163 CVE-2025-53131 CVE-2025-53143 CVE-2025-53144 CVE-2025-53145

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.