Patch tracker / CVE reference / CVE-2025-24067

CVE-2025-24067

CVE-2025-24067 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 59%. 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

59%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2025-24067

The third Kernel Streaming Service driver escalation in this batch, hitting the same Windows 10 1809 and Windows Server 2019 platforms at the same High Severity CVSS 8.8 and the same elevated 59 percent EPSS. At this point the component's track record matters more than the individual CVE: kernel streaming is a proven escalation surface.

Do this: If any systems cannot take the update promptly, watch them for local privilege escalation behavior with your EDR tooling.

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

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

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-24067 (source: https://senserva.com/cve/CVE-2025-24067.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-24067: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 59%
- Actively exploited (CISA KEV): no
- Fixed by: KB5053594, KB5053596, KB5053598, KB5053599, KB5053602, KB5053603, KB5053606, KB5053618, KB5053636, KB5053638
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 59%).

Fixed by KB5053594 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-24067

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5053594, KB5053596, KB5053598, KB5053599, KB5053602, KB5053603, KB5053606, KB5053618, KB5053636, KB5053638 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-24067. 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.

KB5053594 KB5053596 KB5053598 KB5053599 KB5053602 KB5053603 KB5053606 KB5053618 KB5053636 KB5053638

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-24985 CVE-2025-24993 CVE-2025-24983 CVE-2025-26633 CVE-2025-24054 CVE-2025-24991 CVE-2025-24984 CVE-2024-9157

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.