dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-33052

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.17763.7434 / 10.0.19044.5965 or later.
See remediation →
57/100
Remediation priority · Elevated
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 of uninitialized resource in Windows DWM Core Library allows an authorized attacker to disclose information 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

The Windows DWM Core Library (dwmcore.dll) uses an uninitialized resource (likely memory) that allows a locally authenticated attacker to read sensitive information. This is an information disclosure vulnerability in the Desktop Window Manager's core library that processes window rendering and compositing operations.

MitigationApply the Microsoft security update for CVE-2025-33052 through Windows Update or WSUS. For defense-in-depth, ensure users run with least privilege and monitor for unusual DWM activity.

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.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270
Windows Server 2019Operating system
Affected:< 10.0.17763.7434
Windows Server 2022Operating system
Affected:< 10.0.20348.3745

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 and build number
    Open Settings > System > About, or run 'winver' command, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in command prompt
    Affected if The Windows version build number is lower than the affected version ranges listed (e.g., below 17763.7434 for Windows 10 1809/Server 2019, below 19044.5965 for Windows 10 21h2, etc.)
  2. Check dwmcore.dll file version
    Locate dwmcore.dll in C:\Windows\System32\ or C:\Windows\SysWOW64\, right-click > Properties > Details tab, or run 'dir dwmcore.dll' and check the version in the output
    Affected if The file version of dwmcore.dll is lower than the security update version (compare against the affected build numbers for your Windows release)
  3. Verify DWM service is running
    Open Services console (services.msc) and find Desktop Window Manager, or run 'sc query WinDefend' and look for 'RUNNING' status, or run 'tasklist /FI "IMAGENAME eq dwm.exe"'
    Affected if The Desktop Window Manager service (dwm.exe) is running - the vulnerability only affects systems where DWM is active
  4. Check for installed security updates
    Run 'wmic qfe list' or open Control Panel > Programs > Programs and Features > View installed updates, then search for KB references from the CVE-2025-33052 patch month
    Affected if The specific security update for CVE-2025-33052 is not listed among installed updates

A system is affected if it runs a Windows version within the affected build ranges AND has the vulnerable dwmcore.dll version AND has DWM active, and lacks the corresponding 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.17763.7434 / 10.0.19044.5965 / 10.0.19045.5965 or later
Fixed in 10.0.17763.743410.0.19044.596510.0.19045.5965
Interim mitigation

Apply the Microsoft security update for CVE-2025-33052 through Windows Update or WSUS. For defense-in-depth, ensure users run with least privilege and monitor for unusual DWM activity.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.7434 or later | Windows 10 21h2: 10.0.19044.5965 or later | Windows 10 22h2: 10.0.19045.5965 or later | Windows 11 22h2: 10.0.22621.5472 or later | Windows 11 23h2: 10.0.22631.5472 or later | Windows 11 24h2: 10.0.26100.4270 or later | Windows Server 2019: 10.0.17763.7434

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Compare the current build number against the vulnerable versions: Windows 10 1809 < 10.0.17763.7434, Windows 10 21h2 < 10.0.19044.5965, Windows 10 22h2 < 10.0.19045.5965, Windows 11 22h2 < 10.0.22621.5472, Windows 11 23h2 < 10.0.22631.5472, Windows 11 24h2 < 10.0.26100.4270, Windows Server 2019 < 10.0.17763.7434, Windows Server 2022 < 10.0.20348.3745
  3. If the system is vulnerable, run Windows Update (Settings > Update & Security > Windows Update) and install all available security updates
  4. Alternatively, manually download and install the specific KB patch for this vulnerability from the Microsoft Update Catalog
  5. Restart the system after the update is installed
  6. Verify the fix by checking the new build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update; no breaking changes expected for this informational disclosure vulnerability patch

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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