Patch tracker / CVE reference / CVE-2025-33069

CVE-2025-33069

CVE-2025-33069 is a medium severity Microsoft vulnerability with a CVSS score of 5.1. Its EPSS score puts the probability of exploitation in the next 30 days at 85%. Microsoft has shipped the fix: deploy one of the 2 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Medium

5.1

CVSS

85%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability 85%. CVSS 5.1 (Medium).

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

Senserva AI Opinion for CVE-2025-33069

Windows App Control for Business, the application allowlisting feature many hardened environments rely on, has a High severity security feature bypass at CVSS 8.8 affecting Windows Server 2025 Server Core and Windows 11 Version 24H2 on ARM64 and x64. An 82 percent EPSS score, one of the higher probabilities in this batch, means attackers are likely already probing ways to slip unauthorized code past App Control policies.

Do this: Patch Windows Server 2025 Core and Windows 11 24H2 systems that enforce App Control for Business without delay given the high EPSS.

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

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

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

Fixed by KB5060841 and 1 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-33069

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

KB5060841 KB5060842

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-33053 CVE-2025-33073 CVE-2025-33064 CVE-2025-33066 CVE-2025-33067 CVE-2025-29828 CVE-2025-33070 CVE-2025-33071

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.