dbcve.org
Windows 11 26h1Operating system · Microsoft

CVE-2026-58633

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.28000.2525 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
Use after free in Desktop Window Manager 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 · moderate confidence

Use after free vulnerability in Desktop Window Manager (dwm.exe) enables a local authorized attacker to escalate privileges. This memory corruption flaw allows an attacker with local access to potentially execute code at a higher privilege level by manipulating freed memory references.

MitigationApply Microsoft security updates for affected Windows versions promptly; given the local privilege escalation risk, prioritize patching endpoint systems and workstations with direct user 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 11 26h1Operating system
Affected:< 10.0.28000.2525

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. Identify Windows 11 version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to check if the system is Windows 11 version 26h1
    Affected if The system is Windows 11 26h1 (24H2 update) - if running a different Windows version or different Windows 11 update (like 24H2), the system is not affected by this specific CVE
  2. Locate Desktop Window Manager executable
    Find dwm.exe in the system directory, typically C:\Windows\System32\dwm.exe
    Affected if The file exists and is the Desktop Window Manager process used by Windows for compositing visuals
  3. Retrieve dwm.exe file version
    Right-click dwwm.exe, select Properties, then Details tab to view File Version; alternatively run 'wmic datafile where "name='C:\\Windows\\System32\\dwm.exe'" get Version'
    Affected if The dwm.exe file version is displayed and can be compared to the affected version range
  4. Compare version against vulnerable range
    Compare the installed dwm.exe version number to 10.0.28000.2525 - versions lower than 10.0.28000.2525 are vulnerable
    Affected if The dwm.exe version is below 10.0.28000.2525 (for example 10.0.28000.2524 or earlier) on Windows 11 26h1 systems

A system is affected if it runs Windows 11 version 26h1 with dwm.exe version lower than 10.0.28000.2525, as the use-after-free flaw requires the vulnerable Desktop Window Manager component to be present and running.

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.28000.2525 or later
Fixed in 10.0.28000.2525
Interim mitigation

Apply Microsoft security updates for affected Windows versions promptly; given the local privilege escalation risk, prioritize patching endpoint systems and workstations with direct user access.

Recommended fix High confidence

Windows 11 26h1 build 10.0.28000.2525 or later

  1. Open Settings > Windows Update and check for updates
  2. Install all available security updates for Windows 11 26h1
  3. Alternatively, navigate to Microsoft Update Catalog and search for KB article associated with this CVE (check msrc.microsoft.com for the specific KB number)
  4. Restart the system after applying the update
  5. Verify the update was installed by running 'winver' and confirming the build number is 10.0.28000.2525 or higher
Caveat Standard Windows update apply risk - updates may require restart and occasionally cause compatibility issues with third-party software

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

Fix this in Windows 11 26h1 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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