CVE-2025-33069 Overview
CVE-2025-33069 is a security feature bypass vulnerability in Microsoft App Control for Business, formerly known as Windows Defender Application Control (WDAC). The flaw stems from improper verification of cryptographic signatures [CWE-347], allowing a local attacker to bypass application allowlisting controls without prior authentication. Microsoft published the advisory on June 10, 2025, affecting Windows 11 24H2 and Windows Server 2025. Exploitation requires local access to a target system but no user interaction. Successful exploitation undermines the integrity guarantees that App Control for Business enforces on executable code.
Critical Impact
An attacker who bypasses App Control for Business can execute code that policy would otherwise block, weakening the endpoint's application allowlisting defense.
Affected Products
- Microsoft Windows 11 24H2
- Microsoft Windows Server 2025
- Microsoft App Control for Business (WDAC)
Discovery Timeline
- 2025-06-10 - CVE-2025-33069 published to NVD
- 2025-06-10 - Microsoft releases security advisory and guidance
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-33069
Vulnerability Analysis
App Control for Business enforces policy-based restrictions on which binaries, scripts, and drivers can execute on a Windows system. Enforcement depends on validating Authenticode signatures against configured publisher, hash, and file attribute rules. CVE-2025-33069 arises when the signature verification path accepts input that should be rejected, permitting policy-blocked code to run. The vulnerability is scoped to local attack vectors, and the attacker does not require prior authentication or user interaction.
Root Cause
The root cause is improper verification of cryptographic signature [CWE-347] within the App Control for Business enforcement component. Signature validation logic fails to correctly assess trust indicators before allowing an executable to run under enforced policy. Microsoft has not published low-level implementation details beyond the advisory.
Attack Vector
Exploitation requires local access to a Windows 11 24H2 or Windows Server 2025 host that enforces an App Control for Business policy. An attacker stages a binary that would normally be blocked and leverages the signature verification flaw to execute it. Because App Control is designed to constrain what runs on the system, a bypass typically serves as a post-compromise capability that enables adversaries to run untrusted tooling, persistence mechanisms, or defense-evasion payloads. No verified public proof-of-concept exploit is available at this time.
See the Microsoft CVE-2025-33069 Advisory for vendor technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2025-33069
Indicators of Compromise
- Execution of unsigned or improperly signed binaries on hosts with an enforced App Control for Business policy.
- CodeIntegrity operational log entries (Event IDs 3076, 3077, 3089) showing anomalous signature validation outcomes or missing block events for suspicious binaries.
- Newly written executables in user-writable directories that subsequently execute despite policy restrictions.
Detection Strategies
- Monitor the Windows Microsoft-Windows-CodeIntegrity/Operational event channel for gaps between expected block events and observed process creations.
- Correlate Sysmon Event ID 1 (process create) with CodeIntegrity events to identify processes that launched without a corresponding allow decision.
- Baseline signer identities across the fleet and alert on unexpected publishers executing under enforced App Control policies.
Monitoring Recommendations
- Ingest CodeIntegrity, Sysmon, and Windows Security logs into a centralized analytics platform for cross-host correlation.
- Track policy version and enforcement mode drift across Windows 11 24H2 and Windows Server 2025 endpoints.
- Alert on local privilege changes and script interpreter execution that precedes disallowed binary launches.
How to Mitigate CVE-2025-33069
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft CVE-2025-33069 Advisory to all Windows 11 24H2 and Windows Server 2025 systems.
- Inventory endpoints that rely on App Control for Business as a primary allowlisting control and prioritize them for patching.
- Restrict local logon rights and remove unnecessary local administrator access to reduce the exploitable attack surface.
Patch Information
Microsoft addressed CVE-2025-33069 in the June 10, 2025 security update cycle. Refer to the Microsoft CVE-2025-33069 Advisory for the specific update packages that apply to Windows 11 24H2 and Windows Server 2025 builds in your environment.
Workarounds
- Enforce App Control policies in audit mode alongside enforcement mode on critical systems to increase telemetry visibility.
- Layer additional application control with AppLocker rules and constrained language mode for PowerShell where feasible.
- Limit interactive local access to trusted administrators and require multi-factor authentication for privileged sessions.
# Verify App Control for Business policy status on affected hosts
CiTool.exe --list-policies
# Confirm required Windows security update is installed
Get-HotFix | Where-Object { $_.InstalledOn -ge '2025-06-10' }
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

