CVE-2025-26678

8.4 HIGH

📋 TL;DR

CVE-2025-26678 is an improper access control vulnerability in Windows Defender Application Control (WDAC) that allows local attackers to bypass security restrictions. This affects Windows systems using WDAC policies for application control. Attackers could execute unauthorized code despite WDAC protections.

💻 Affected Systems

Products:
  • Windows Defender Application Control (WDAC)
Versions: Specific Windows versions not yet detailed in initial advisory
Operating Systems: Windows 10, Windows 11, Windows Server 2016+, Windows Server 2022
Default Config Vulnerable: ✅ No
Notes: Only affects systems where WDAC policies are actively deployed and enforced. Systems without WDAC enabled are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete local privilege escalation leading to full system compromise, persistence establishment, and lateral movement within the network.

🟠

Likely Case

Local attackers bypass application control policies to execute malicious software, install unauthorized applications, or evade security monitoring.

🟢

If Mitigated

Limited impact with proper network segmentation, least privilege principles, and additional security controls in place.

🌐 Internet-Facing: LOW - This is a local privilege escalation requiring local access to the system.
🏢 Internal Only: HIGH - Internal attackers with standard user access could exploit this to bypass security controls and escalate privileges.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires local access and some technical knowledge of WDAC bypass techniques. No public exploit code available at initial disclosure.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Microsoft Security Update Guide for specific KB numbers

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26678

Restart Required: Yes

Instructions:

1. Apply latest Windows security updates from Microsoft. 2. For WDAC-managed systems, ensure policies are updated after patching. 3. Restart affected systems to complete installation.

🔧 Temporary Workarounds

Temporarily disable WDAC

windows

Disable WDAC policies until patching can be completed (increases risk of other attacks)

Set-ProcessMitigation -Disable WDAC

Implement additional application control layers

windows

Use AppLocker or third-party application control alongside WDAC for defense in depth

🧯 If You Can't Patch

  • Implement strict network segmentation to limit lateral movement from compromised systems
  • Enforce least privilege access controls and monitor for unusual local privilege escalation attempts

🔍 How to Verify

Check if Vulnerable:

Check if WDAC is enabled and verify Windows version against patched versions in Microsoft advisory

Check Version:

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

Verify Fix Applied:

Verify Windows Update history contains the relevant security update and test WDAC policy enforcement

📡 Detection & Monitoring

Log Indicators:

  • Windows Security logs showing WDAC policy bypass events
  • Event ID 3076/3077 in Application logs indicating policy violations

Network Indicators:

  • Unusual outbound connections from systems with WDAC policies after local compromise

SIEM Query:

EventID=3076 OR EventID=3077 | where ProcessName contains suspicious executable names

🔗 References

📤 Share & Export