Patch tracker / CVE reference / CVE-2025-50174

CVE-2025-50174

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

Risk summary

High

7.0

CVSS

6.0%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 6.0%. CVSS 7.0 (High).

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

Senserva AI Opinion for CVE-2025-50174

This Device Association Broker Service bug carries a 9.9 CVSS score, the highest severity rating in this entire batch, though its EPSS exploit probability is a modest 6 percent. It affects Windows 11 25H2 and Windows Server 2025 Server Core, both relatively new builds. The near-maximum CVSS score reflects how completely the flaw can be abused once exploited, even if attackers have not yet gravitated to it. No confirmed KEV or ransomware activity.

Do this: Do not let the modest EPSS score delay this patch given its 9.9 severity; treat it as a priority fix on Windows 11 25H2 and Server 2025.

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

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

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

Fixed by KB5066835. 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-50174

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing update KB5066835 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security update below to fix CVE-2025-50174. 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.

KB5066835

Scope and sources

Affected products

Fixed by the same update

CVE-2025-24990 CVE-2025-59230 CVE-2025-47827 CVE-2016-9535 CVE-2025-49708 CVE-2025-59280 CVE-2025-59284 CVE-2025-59294

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.