Patch tracker / CVE reference / CVE-2025-49739

CVE-2025-49739

CVE-2025-49739 is a high severity Microsoft vulnerability with a CVSS score of 8.8. 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

8.8

CVSS

<1%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2025-49739

CVE-2025-49739 is an elevation of privilege flaw in Microsoft Visual Studio that spans a wide range of releases, from the older 2017 line (15.0 through 15.9) up through 2019 (16.0 through 16.11) and 2022 version 17.12. The exposure here is developer workstations and build machines rather than servers, so it matters most for engineering teams whose developers run with local accounts that an attacker could escalate. Despite the High severity and CVSS 8.8, EPSS is only 1 percent and there is no confirmed exploitation or ransomware use.

Do this: Push the Visual Studio updates to all developer and build machines running the 2017, 2019, and 2022 branches, prioritizing any still on the older 15.x installs.

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

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

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

Fixed by KB5063035. 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-49739

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing update KB5063035 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-49739. 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.

KB5063035

Scope and sources

Affected products

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.