dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-33069

MEDIUM · 5.1 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.26100.4270 or later.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper verification of cryptographic signature in App Control for Business (WDAC) allows an unauthorized attacker to bypass a security feature locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Windows Defender Application Control (WDAC) contains a flaw in cryptographic signature verification that allows a local attacker to bypass WDAC security policies and execute unsigned or malicious code that would normally be blocked.

MitigationDeploy the Microsoft security update for CVE-2025-33069 when released and verify WDAC policies continue to enforce code signing requirements after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270
Windows Server 2025Operating system
Affected:< 10.0.26100.4270

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows edition and version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows edition and build number.
    Affected if The system is running Windows 11 24h2 or Windows Server 2025 with a build number lower than 10.0.26100.4270.
  2. Retrieve exact build number
    Open Command Prompt or PowerShell and run 'ver' or check the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' for the 'CurrentBuild' and 'DisplayVersion' values.
    Affected if The 'CurrentBuild' number is less than 26100, or the full build string is below 10.0.26100.4270.
  3. Verify WDAC is enabled
    Run 'Get-CimInstance -ClassName Win32_ComputerSystem | Select-Object -Property Name' and then check the WDAC status via 'Get-CimInstance -Namespace root/Microsoft/Windows/CI -ClassName CEIP' or review Group Policy at Computer Configuration > Windows Settings > Security Settings > Code Integrity > Code Integrity Options.
    Affected if WDAC policies are active on the system, as the vulnerability only impacts environments where WDAC is enforcing code signing policies.
  4. Check for recent security updates
    Run 'powershell Get-HotFix | Where-Object {$_.Description -match "Security"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' or view the Windows Update history in Settings > Windows Update > Update history.
    Affected if No security update addressing CVE-2025-33069 has been installed, and the system build remains vulnerable.

A system is affected if it runs Windows 11 24h2 or Windows Server 2025 with a build below 10.0.26100.4270 and has WDAC policies enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.26100.4270 or later
Fixed in 10.0.26100.4270
Interim mitigation

Deploy the Microsoft security update for CVE-2025-33069 when released and verify WDAC policies continue to enforce code signing requirements after patching.

Recommended fix High confidence

Windows 11 24h2 and Windows Server 2025 - Build 10.0.26100.4270 or later

  1. Open Settings > System > Windows Update and check for updates
  2. Install all available updates including the security update containing build 10.0.26100.4270
  3. Restart the system if prompted to complete the installation
  4. Verify the update was successful by running 'winver' in the command prompt and confirming the build number matches or exceeds 10.0.26100.4270

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33069 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data