dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-58541

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 5 weeks old

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
Access of resource using incompatible type ('type confusion') in Windows DWM allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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 · high confidence

A type confusion vulnerability in Windows Desktop Window Manager (DWM) allows a local authenticated attacker to elevate privileges by exploiting how DWM handles resource types, potentially executing code with higher permissions.

MitigationApply Microsoft security updates for Windows DWM promptly; prioritize systems with exposed local attack surfaces.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2016Operating system
Affected:< 10.0.14393.9339

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' from command prompt or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number
    Affected if The build number is less than the fixed version for your Windows release (e.g., < 10.0.14393.9339 for Windows 10 1607/Server 2016, < 10.0.17763.9020 for Windows 10 1809, etc.)
  2. Verify DWM service is running
    Run 'Get-Process dwm*' or 'tasklist /FI "IMAGENAME eq dwm.exe"' from an elevated command prompt to check if the Desktop Window Manager process is active
    Affected if DWM.exe is running (typical on Windows desktop editions, less common on Server Core installations)
  3. Confirm Windows edition type
    Run 'systeminfo | findstr /C:"System Type" /C:"Installation Type"' to determine if this is a desktop or server installation
    Affected if Running a desktop Windows edition (not Server Core) where DWM is enabled and the version is below the fixed builds

You are affected if DWM.exe is running on a Windows version whose build number falls below the fixed version for your specific Windows release.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security updates for Windows DWM promptly; prioritize systems with exposed local attack surfaces.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9339 | Windows 10 1809: 10.0.17763.9020 | Windows 10 21h2: 10.0.19044.7548 | Windows 10 22h2: 10.0.19045.7548 | Windows 11 24h2: 10.0.26100.8875 | Windows 11 25h2: 10.0.26200.8875 | Windows 11 26h1: 10.0.28000.2269 | Windows Server 2016: 10.0.14393.9339

  1. Open Settings on the Windows system and navigate to Windows Update
  2. Click 'Check for updates' and install all available updates, including the security update for this CVE
  3. Alternatively, manually download the appropriate cumulative update from the Microsoft Update Catalog for your Windows version
  4. For enterprise environments, deploy the update via WSUS, SCCM, or Group Policy
  5. After installation, restart the system to apply the changes
  6. Verify the installed version matches or exceeds the fixed build number for your Windows version
Caveat Standard Windows update apply risks - update has been tested by Microsoft for compatibility; may require restart

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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