Patch tracker / CVE reference / CVE-2025-49665

CVE-2025-49665

CVE-2025-49665 is a high severity Microsoft vulnerability with a CVSS score of 7.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 10 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.8

CVSS

32%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 32%. CVSS 7.8 (High).

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

Senserva AI Opinion for CVE-2025-49665

The Workspace Broker component has an elevation of privilege vulnerability rated Critical Severity at CVSS 9.8 with a 22 percent EPSS score, affecting Windows 10 1809 and Server 2019. Broker processes exist to mediate between low-privilege apps and privileged operations, which puts them permanently on the privilege boundary where escalation bugs live. It is one of an unusually long list of Critical Severity broker and service escalation fixes this cycle.

Do this: Verify rollup compliance across 1809 and Server 2019 rather than triaging each broker bug separately.

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

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

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-49665 (source: https://senserva.com/cve/CVE-2025-49665.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-49665: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 32%
- Actively exploited (CISA KEV): no
- Fixed by: KB5062552, KB5062553, KB5062554, KB5062557, KB5062560, KB5062561, KB5062570, KB5062572, KB5062592, KB5062597
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 32%).

Fixed by KB5062552 and 9 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-49665

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 KB5062552, KB5062553, KB5062554, KB5062557, KB5062560, KB5062561, KB5062570, KB5062572, KB5062592, KB5062597 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-49665. 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.

KB5062552 KB5062553 KB5062554 KB5062557 KB5062560 KB5062561 KB5062570 KB5062572 KB5062592 KB5062597

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-47981 CVE-2025-49760 CVE-2025-47986 CVE-2025-47998 CVE-2025-48817 CVE-2025-48824 CVE-2025-49657 CVE-2025-49663

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.