dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49664

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 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
Exposure of sensitive information to an unauthorized actor in Windows User-Mode Driver Framework Host 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

This is a local information disclosure vulnerability in the Windows User-Mode Driver Framework Host (UMDF). An authorized attacker with local access to the system can exploit this to disclose sensitive information. The vulnerability stems from improper access controls within the UMDF host process that manages user-mode drivers.

MitigationApply the relevant Microsoft security update for Windows when released. Prioritize patching endpoints with access to sensitive data or those frequently used by authorized local users. Verify that least-privilege principles are enforced for local user accounts.

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 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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 build version
    Open Command Prompt or PowerShell and run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to display the installed Windows version and build number
    Affected if The build number is lower than the fixed versions (10.0.10240.21073 for 1507, 10.0.14393.8246 for 1607, 10.0.17763.7558 for 1809, 10.0.19044.6093 for 21h2, 10.0.19045.6093 for 22h2, 10.0.22621.5624 for Win11 22h2, 10.0.22631.5624 for Win11 23h2, or 10.0.26100.4652 for Win11 24h2)
  2. Confirm Windows release branch
    Identify whether the system is Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2 by checking the build number against known release timelines
    Affected if The identified release branch matches one of the affected versions and its build falls below the corresponding fixed threshold
  3. Verify UMDF host process presence
    Check if the UMDF host process exists by looking for WudfHost.exe in the system: `dir /s C:\Windows\System32\WudfHost.exe` or `Get-ChildItem -Path C:\Windows\System32 -Filter WudfHost.exe -Recurse` in PowerShell
    Affected if WudfHost.exe exists on the system (the vulnerability exists in this component)

A system is affected if it runs any of the listed Windows versions below the specified build numbers and has the UMDF host process present, as the improper access controls in that component can be exploited by a local attacker to disclose sensitive information.

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.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the relevant Microsoft security update for Windows when released. Prioritize patching endpoints with access to sensitive data or those frequently used by authorized local users. Verify that least-privilege principles are enforced for local user accounts.

Recommended fix High confidence

Install the appropriate Windows security update from Windows Update that addresses CVE-2025-49664 (fixed builds: Windows 10 1507: 10.0.10240.21073, Windows 10 1607: 10.0.14393.8246, Windows 10 1809: 10.0.17763.7558, Windows 10 21h2: 10.0.19044.6093, Windows 10 22h2: 10.0.19045.6093, Windows 11 22h2:

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update (Settings > Windows Update)
  3. Check for updates and install all available updates
  4. Restart the system if prompted
  5. Verify the installed Windows version matches or exceeds the fixed build number for your Windows version
Caveat Standard Windows update; ensure backups of critical data before applying updates as a precaution

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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