Patch tracker / CVE reference / CVE-2025-47969

CVE-2025-47969

CVE-2025-47969 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 61%. Microsoft has shipped the fix: deploy one of the 3 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

61%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2025-47969

Windows Virtualization-Based Security, the foundation behind Credential Guard and memory integrity, has a High severity information disclosure vulnerability at CVSS 8.8 affecting Windows 11 Version 22H2 (ARM64 and x64) and Windows Server 2025 Server Core. Since VBS underpins several other Windows security features, a leak here can weaken protections that many organizations assume are airtight. EPSS is 58 percent.

Do this: Patch Windows 11 22H2 and Server 2025 systems that rely on VBS-backed protections like Credential Guard.

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

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

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

Fixed by KB5058405 and 2 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-47969

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5058405, KB5058411, KB5058497 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-47969. 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.

KB5058405 KB5058411 KB5058497

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-30400 CVE-2025-32701 CVE-2025-32706 CVE-2025-32709 CVE-2025-30397 CVE-2025-29839 CVE-2025-29840 CVE-2025-29962

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.