dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-58722

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.14393.8519 / 10.0.17763.7919 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 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 the Windows Desktop Window Manager (DWM) allows a local authenticated attacker to corrupt heap memory and elevate privileges to higher integrity levels, potentially achieving SYSTEM or administrator access.

MitigationApply the Microsoft security update for CVE-2025-58722 immediately upon release; restrict local access to privileged accounts and monitor for anomalous DWM process 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 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
Windows 11 25h2Operating system
Affected:< 10.0.26200.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. Check installed Windows build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the full version and build
    Affected if The build number falls below any of these thresholds: 14393.8519 (Win10 1607), 17763.7919 (Win10 1809), 19044.6456 (Win10 21h2/22h2), 22621.6060 (Win11 22h2), 22631.6060 (Win11 23h2), 26100.6899 (Win11 24h2), 26200.6899 (Win11 25h2)
  2. Confirm Windows edition matches affected list
    Run 'winver' to see the exact Windows edition (Home, Pro, Enterprise, etc.) and confirm it is Windows 10 or Windows 11
    Affected if The system runs Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, 24h2, or 25h2 with a vulnerable build number
  3. Verify if DWM is running
    Open Task Manager, go to Details tab, and look for dwm.exe in the list, or run 'tasklist | findstr dwm' in Command Prompt
    Affected if DWM process is running (this is the vulnerable component that must be present for exploitation)
  4. Check installed security updates for CVE-2025-58722
    Open PowerShell and run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security patches, or check Windows Update history for the specific CVE
    Affected if No security update addressing CVE-2025-58722 is installed and the Windows build is in the affected range

A system is affected if it runs a Windows 10 or 11 version with a build number lower than the fixed thresholds AND lacks the CVE-2025-58722 security update.

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.14393.8519 / 10.0.17763.7919 / 10.0.19044.6456 or later
Fixed in 10.0.14393.851910.0.17763.791910.0.19044.6456
Interim mitigation

Apply the Microsoft security update for CVE-2025-58722 immediately upon release; restrict local access to privileged accounts and monitor for anomalous DWM process behavior.

Recommended fix High confidence

Install the appropriate Windows security update (KB5055527 or later) which upgrades DWM to the fixed build version for your Windows release (e.g., Windows 10 22h2 to 10.0.19045.6456+, Windows 11 24h2 to 10.0.26100.6899+)

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative update
  3. Alternatively, manually download the security update from the Microsoft Update Catalog for your specific Windows version: KB5055527 (or later)
  4. Restart the system after installing the update
  5. Verify the installed update by running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update; may require restart; no expected breaking changes for this security patch

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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