dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Jun 2025.
Windows 10 1809Operating system · Microsoft

CVE-2025-30400

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.17763.7314 / 10.0.19044.5854 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild 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 Windows DWM 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 Windows Desktop Window Manager (DWM) enables a locally authenticated attacker to achieve privilege escalation by manipulating memory after a heap object has been freed, leading to arbitrary code execution at elevated privilege levels.

MitigationApply Microsoft security updates for CVE-2025-30400 when released; until then, limit local access to trusted users and monitor for suspicious DWM child 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 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.3981
Windows Server 2019Operating system
Affected:< 10.0.17763.7314
Windows Server 2022Operating system
Affected:< 10.0.20348.3692

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' from command prompt or 'systeminfo' and locate the OS Name and Version lines, or query the registry with 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild'
    Affected if The build number falls below the threshold for your Windows release: 17763.7314 for Windows 10 1809/Server 2019, 19044.5854 for Windows 10 21h2, 19045.5854 for Windows 10 22h2, 22621.5335 for Windows 11 22h2, 22631.5335 for Windows 11 23h2, 26100.3981 for Windows 11 24h2, or 20348.3692 for Windows S
  2. Confirm DWM process is running
    Open Task Manager, go to the Processes or Details tab, and look for 'Desktop Window Manager (dwm.exe)' or run 'tasklist /FI "IMAGENAME eq dwm.exe"' from command prompt
    Affected if The DWM process is present and running, which is the default state on Windows desktop editions and typically on Windows Server with Desktop Experience installed
  3. Check installed KB patches for CVE-2025-30400
    Run 'wmic qfe get hotfixid,installedon' or check Windows Update history in Settings > Windows Update > Update history for security updates installed after the vulnerability disclosure date
    Affected if No security update corresponding to CVE-2025-30400 appears in the installed hotfix list

You are affected if your Windows version build is below the threshold for your specific release AND the DWM process is running AND no corresponding security patch has been installed.

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.17763.7314 / 10.0.19044.5854 / 10.0.19045.5854 or later
Fixed in 10.0.17763.731410.0.19044.585410.0.19045.5854
Interim mitigation

Apply Microsoft security updates for CVE-2025-30400 when released; until then, limit local access to trusted users and monitor for suspicious DWM child processes.

Recommended fix High confidence

Upgrade to the latest Windows security update containing the fix: Windows 10 1809 (10.0.17763.7314+), Windows 10 21h2 (10.0.19044.5854+), Windows 10 22h2 (10.0.19045.5854+), Windows 11 22h2 (10.0.22621.5335+), Windows 11 23h2 (10.0.22631.5335+), Windows 11 24h2 (10.0.26100.3981+), Windows Server 201

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates, ensuring the update containing the fix for CVE-2025-30400 is applied
  4. Restart the system after updates are installed
  5. Verify the fix by checking the installed Windows version matches or exceeds: 10.0.17763.7314 (Windows 10 1809/Server 2019), 10.0.19044.5854 (Windows 10 21h2), 10.0.19045.5854 (Windows 10 22h2), 10.0.22621.5335 (Windows 11 22h2), 10.0.22631.5335 (Windows 11 23h2), 10.0.26100.3981 (Windows 11 24h2), or 10.0.20348.3692 (Windows Server 2022)
Caveat Standard Windows update; review release notes for any known issues specific to the target environment

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

Fix this in Windows 10 1809 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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