dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-34336

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 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
Integer overflow or wraparound 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

A vulnerability in the Windows Desktop Window Manager (DWM) Core Library involves an integer overflow or wraparound condition that can be exploited by a local, authorized attacker to escalate privileges to a higher integrity level.

MitigationApply the Microsoft security update for this vulnerability through Windows Update or enterprise patch management systems to address the integer overflow in the DWM Core Library.

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.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

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. Determine Windows build version
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the full build number including the revision (e.g., 10.0.14393.9140)
    Affected if The displayed build number is lower than any of the listed thresholds for your Windows version (10.0.14393.9140 for 1607, 10.0.17763.8755 for 1809, 10.0.19044.7291 for 21h2, 10.0.19045.7291 for 22h2, 10.0.22631.7079 for 23h2, 10.0.26100.8390 for 24h2, 10.0.26200.8390 for 25h2, or 10.0.28000.2113 for
  2. Confirm DWM Core Library is in use
    Verify that the Desktop Window Manager (dwm.exe) process is running. Open Task Manager, go to the Details tab, and look for dwm.exe, or run 'tasklist | findstr dwm.exe' from command prompt
    Affected if dwm.exe is running (this is the component containing the vulnerable DWM Core Library)
  3. Check for pending security updates
    Open Windows Settings > Windows Update > Update History and look for recent security updates related to Windows, or check 'wmic qfe list' to see installed hotfixes
    Affected if The system has not received the Microsoft security update for this specific CVE (no corresponding KB or security patch is listed in update history)

You are affected if your Windows build number falls below the threshold for your specific Windows version AND the DWM Core Library is active on your system.

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.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply the Microsoft security update for this vulnerability through Windows Update or enterprise patch management systems to address the integer overflow in the DWM Core Library.

Recommended fix Moderate confidence

Upgrade to the minimum fixed build for your Windows version (e.g., Windows 10 1809: 10.0.17763.8755 or later)

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or Windows 11 version and build is currently installed
  3. For Windows 10 1607: Upgrade to Windows 10 build 10.0.14393.9140 or later
  4. For Windows 10 1809: Upgrade to Windows 10 build 10.0.17763.8755 or later
  5. For Windows 10 21h2: Upgrade to Windows 10 build 10.0.19044.7291 or later
  6. For Windows 10 22h2: Upgrade to Windows 10 build 10.0.19045.7291 or later
  7. For Windows 11 23h2: Upgrade to Windows 11 build 10.0.22631.7079 or later
  8. For Windows 11 24h2: Upgrade to Windows 11 build 10.0.26100.8390 or later
Caveat Standard Windows security update with minimal risk; ensure backups and test in non-production environments before broad deployment

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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