dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53152

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 execute code 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 Windows Desktop Window Manager (dwm.exe) allows a locally authorized attacker to execute arbitrary code by corrupting memory through accessing freed heap allocations.

MitigationApply Microsoft security updates for CVE-2025-53152 once released; until then, minimize local attack surface by restricting user privileges and monitoring for unusual DWM behavior.

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 and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows version and build number
    Affected if The build number falls below the safe thresholds: < 10.0.10240.21100 (1507), < 10.0.14393.8330 (1607), < 10.0.17763.7678 (1809), < 10.0.19044.6216 (21h2), < 10.0.19045.6216 (22h2), < 10.0.22621.5768 (Win11 22h2), < 10.0.22631.5768 (Win11 23h2), or is Windows Server 2008 R2 at any version
  2. Confirm DWM process is running
    Run 'tasklist /FI "IMAGENAME eq dwm.exe"' or 'Get-Process dwm' in PowerShell to verify the Desktop Window Manager is active
    Affected if DWM is not running (though this is uncommon on desktop Windows, as DWM is required for Aero glass and visual effects)
  3. Check if running Windows Server 2008 R2
    Run 'systeminfo' and verify the OS is Windows Server 2008 R2 at any build
    Affected if The system is Windows Server 2008 R2 - this version is explicitly listed as affected regardless of build number

You are affected if your Windows build is below the safe thresholds listed or if you are running Windows Server 2008 R2, and DWM is active (which it normally is on desktop Windows).

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 CVE-2025-53152 once released; until then, minimize local attack surface by restricting user privileges and monitoring for unusual DWM behavior.

Recommended fix High confidence

Install the Microsoft security update for CVE-2025-53152 (check Microsoft Update Catalog for the specific KB article) and upgrade to the minimum fixed build for your Windows version

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10 1507: Upgrade to build 10.0.10240.21100 or later
  3. For Windows 10 1607: Upgrade to build 10.0.14393.8330 or later
  4. For Windows 10 1809: Upgrade to build 10.0.17763.7678 or later
  5. For Windows 10 21h2: Upgrade to build 10.0.19044.6216 or later
  6. For Windows 10 22h2: Upgrade to build 10.0.19045.6216 or later
  7. For Windows 11 22h2: Upgrade to build 10.0.22621.5768 or later
  8. For Windows 11 23h2: Upgrade to build 10.0.22631.5768 or later
Caveat Windows Server 2008 R2 is end-of-life with no security updates; migration to a supported Windows Server version is required

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

Fix this in Windows 10 1507 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-53152 — 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-53152 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