Patch tracker / CVE reference / CVE-2025-48809

CVE-2025-48809

CVE-2025-48809 is a medium severity Microsoft vulnerability with a CVSS score of 5.5. Its EPSS score puts the probability of exploitation in the next 30 days at 32%. 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

Medium

5.5

CVSS

32%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability 32%. CVSS 5.5 (Medium).

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

Senserva AI Opinion for CVE-2025-48809

This bug sits in Secure Kernel Mode, the hardware-isolated component behind Virtualization-Based Security, affecting Windows Server 2025, its Core build, and Windows 11 Version 24H2 on ARM64 at Critical 9.8 with 22 percent EPSS. Secure Kernel Mode exists specifically to protect against kernel-level compromise, so a disclosure bug there undermines a defense that many organizations rely on for credential and code-integrity protection. This deserves attention on any system where VBS or Credential Guard is enabled.

Do this: Prioritize this fix on Server 2025, Server 2025 Core, and Windows 11 24H2 ARM64 systems that have Virtualization-Based Security or Credential Guard enabled.

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

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

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

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 update KB5062553 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-48809. 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.

KB5062553

Scope and sources

Affected products

Fixed by the same update

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.