dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-64679

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 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
Heap-based buffer overflow in Windows DWM Core Library 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

Heap-based buffer overflow in Windows DWM Core Library (dwmcore.dll) allows a local authenticated attacker to corrupt heap memory and elevate privileges from their current user context to SYSTEM or administrator-level access.

MitigationApply Microsoft security updates addressing this vulnerability through standard Windows Update or WSUS deployment; prioritize patching systems where untrusted local users have access.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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. Locate the DWM Core Library file
    Open File Explorer and navigate to C:\Windows\System32\dwmcore.dll, or run `dir C:\Windows\System32\dwmcore.dll` in Command Prompt
    Affected if The file does not exist on the system (this would be unusual for a standard Windows installation)
  2. Retrieve the dwmcore.dll file version
    Right-click dwmcore.dll, select Properties, then go to the Details tab. Alternatively, run `powershell (Get-Item 'C:\Windows\System32\dwmcore.dll').VersionInfo` in PowerShell
    Affected if The file version shown is lower than any of the following: 10.0.10240.21161, 10.0.14393.8519, 10.0.17763.7919, 10.0.19044.6456, 10.0.19045.6456, 10.0.22621.6060, 10.0.22631.6060, or 10.0.26100.6899 depending on your Windows version
  3. Identify the installed Windows version and build
    Run `winver` from the Run dialog, or run `powershell [System.Environment]::OSVersion.Version` and `powershell (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuild` in PowerShell
    Affected if The Windows build number matches any of the following: 1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2 with a build lower than 21161, 8519, 7919, 6456, 6456, 6060, 6060, or 6899 respectively

If dwmcore.dll exists and its version or the Windows build number falls below the affected thresholds listed above, the system is potentially vulnerable to this privilege escalation flaw.

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply Microsoft security updates addressing this vulnerability through standard Windows Update or WSUS deployment; prioritize patching systems where untrusted local users have access.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21161 | Windows 10 1607: 10.0.14393.8519 | Windows 10 1809: 10.0.17763.7919 | Windows 10 21h2: 10.0.19044.6456 | Windows 10 22h2: 10.0.19045.6456 | Windows 11 22h2: 10.0.22621.6060 | Windows 11 23h2: 10.0.22631.6060 | Windows 11 24h2: 10.0.26100.6899

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update (or check for updates via Control Panel)
  3. Click 'Check for updates' and allow the system to scan Microsoft Update
  4. Install all available updates, specifically looking for the security update containing the CVE-2025-64679 fix
  5. Restart the system when prompted to complete the installation
  6. Verify the installed Windows version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update apply risks - test critical applications before deployment in production environments

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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