dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-50153

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 or later.
See remediation →
80/100
Remediation priority · High
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
Use after free in Desktop Windows Manager allows an authorized attacker to elevate privileges 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

Use-after-free vulnerability in Desktop Windows Manager (DWM) that allows a local attacker with existing authorization to elevate privileges. The vulnerability involves memory being accessed after it has been freed, leading to arbitrary code execution at elevated privilege levels.

MitigationApply Microsoft security updates for this vulnerability once released. Until patch is available, minimize local attack surface by restricting administrative access and monitoring for suspicious DWM processes.

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 10 1507Operating system
Affected:< 10.0.10240.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows Server 2008Operating system
Affected:= r2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your installed Windows version and build number
    Affected if The version and build number fall below any of the listed thresholds (10.0.10240.21100, 10.0.14393.8330, 10.0.17763.7678, 10.0.19044.6216, 10.0.19045.6216, 10.0.22621.5768, 10.0.22631.5768) or is Windows Server 2008 R2
  2. Verify DWM process is running
    Open Task Manager, go to Details tab, and look for 'dwm.exe' or run 'tasklist | findstr dwm' in Command Prompt
    Affected if The dwm.exe process is present and running (DWM is actively servicing the desktop session)
  3. Confirm DWM service status
    Run 'sc query DwmSvc' in Command Prompt or check Services.msc for the Desktop Window Manager service
    Affected if The Desktop Window Manager service is in a Running state
  4. Check if Desktop Experience feature is installed (Windows Server)
    On Windows Server, run 'Get-WindowsFeature Desktop-Experience' in PowerShell or check Server Manager
    Affected if Desktop Experience feature is installed and the DWM service is running

Your environment is affected if you are running any of the affected Windows versions listed and the DWM process/service is actively running on the system.

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.10240.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply Microsoft security updates for this vulnerability once released. Until patch is available, minimize local attack surface by restricting administrative access and monitoring for suspicious DWM processes.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21100+ | Windows 10 1607: 10.0.14393.8330+ | Windows 10 1809: 10.0.17763.7678+ | Windows 10 21h2: 10.0.19044.6216+ | Windows 10 22h2: 10.0.19045.6216+ | Windows 11 22h2: 10.0.22621.5768+ | Windows 11 23h2: 10.0.22631.5768+ | Windows Server 2008 R2: Latest supported securi

  1. Check current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update and check for updates
  3. Install all available Windows security updates, specifically the patch for CVE-2025-50153
  4. Alternatively, manually download and install the security update from the Microsoft Update Catalog for your specific Windows version
  5. Restart the system after installing the update
  6. Verify the build version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update; review KB article for any known issues before deployment in enterprise environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50153 — 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-50153 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