dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-44802

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.17763.8880 / 10.0.19044.7417 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
Use after free 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 use-after-free vulnerability in the Windows Desktop Window Manager (DWM) Core Library allows a locally authorized attacker to exploit freed memory and elevate privileges to higher integrity levels.

MitigationApply the relevant Microsoft security patches for Windows systems; prioritize workstations and servers running desktop experience components.

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 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2019Operating system
Affected:< 10.0.17763.8880

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 version build number
    Run 'winver' from the command prompt or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the full build number including the revision (e.g., 10.0.19045.7417)
    Affected if The displayed build number falls below any of these thresholds: 17763.8880, 19044.7417, 19045.7417, 22631.7219, 26100.8655, 26200.8655, or 28000.2269 depending on your Windows release
  2. Identify Windows release name and build
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and '/v UBR' to get the exact build and revision number
    Affected if The combined build.revision number (CurrentBuild.UBR) is lower than the version-specific thresholds for your Windows release
  3. Confirm DWM Core Library is in use
    Verify the Desktop Window Manager (DWM) process is running by opening Task Manager, looking under the 'Processes' or 'Details' tab for 'Desktop Window Manager' (dwm.exe), or running 'tasklist /FI "IMAGENAME eq dwm.exe"'
    Affected if DWM is actively running (this is the default state on desktop Windows editions; Server Core installations may not be affected as DWM is typically absent)
  4. Verify Windows edition and release channel
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to confirm the Windows edition (Home, Pro, Enterprise) and release (like 21h2, 22h2, 23h2)
    Affected if The system is any Windows 10 or Windows 11 desktop edition, or Windows Server 2019, with a build number below the patched versions listed for that specific release

A user is affected if their Windows system runs a build number lower than the threshold for their specific Windows release (10.x.yyyy.zzzz where yyyy.zzzz is below the version-specific cutoff) and has DWM enabled, which is the default state on desktop Windows editions.

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.17763.8880 / 10.0.19044.7417 / 10.0.19045.7417 or later
Fixed in 10.0.17763.888010.0.19044.741710.0.19045.7417
Interim mitigation

Apply the relevant Microsoft security patches for Windows systems; prioritize workstations and servers running desktop experience components.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows version (e.g., Windows 10 1809/Server 2019 to 10.0.17763.8880, Windows 11 23h2 to 10.0.22631.7219, etc.)

  1. Identify the current Windows version by running 'winver' or checking System Information
  2. Determine if your current build number is below the fixed version for your Windows edition
  3. For Windows 10 1809/Windows Server 2019: Update to build 10.0.17763.8880 or later
  4. For Windows 10 21h2: Update to build 10.0.19044.7417 or later
  5. For Windows 10 22h2: Update to build 10.0.19045.7417 or later
  6. For Windows 11 23h2: Update to build 10.0.22631.7219 or later
  7. For Windows 11 24h2: Update to build 10.0.26100.8655 or later
  8. For Windows 11 25h2: Update to build 10.0.26200.8655 or later
Caveat Standard Windows update risks apply - ensure backup of critical data before applying system updates

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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