dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-50175

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 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 Digital Media 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 exists in Windows Digital Media where memory is accessed after being freed, enabling a locally authorized attacker to escalate privileges to higher permission levels.

MitigationApply Microsoft security updates for CVE-2025-50175 immediately to all affected Windows systems; prioritize endpoints given the local privilege elevation vector.

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.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2019Operating system
Affected:< 10.0.17763.7919

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 Windows version and build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Version" or [System.Environment]::OSVersion.Version
    Affected if The reported version/build is lower than the fixed versions: 10.0.17763.7919 (Win10 1809/Server 2019), 10.0.19044.6456 (Win10 21h2), 10.0.19045.6456 (Win10 22h2), 10.0.22621.6060 (Win11 22h2), 10.0.22631.6060 (Win11 23h2), 10.0.26100.6899 (Win11 24h2), 10.0.26200.6899 (Win11 25h2)
  2. Confirm Windows edition and release
    Run: winver to see the exact Windows release (such as 'Version 22H2' or 'Version 24H2') and compare against the affected version list
    Affected if Running an affected Windows 10 or 11 release or Windows Server 2019 with a build number below the corresponding fixed threshold
  3. Verify Digital Media component presence
    Check if Windows Digital Media related services or components are running: Get-Process | Where-Object {$_.ProcessName -like "*Media*"} or check Digital Media libraries in System32 such as dm*.dll
    Affected if Digital Media components exist on the system (standard on consumer Windows installations); combined with vulnerable version, the system is exploitable

You are affected if your Windows 10/11 or Windows Server 2019 system has a build number lower than the fixed version for your specific release, and the Windows Digital Media component is present on the 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.17763.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply Microsoft security updates for CVE-2025-50175 immediately to all affected Windows systems; prioritize endpoints given the local privilege elevation vector.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2025-50175 - specific version numbers: Windows 10 1809: 10.0.17763.7919 | Windows 10 21h2: 10.0.19044.6456 | Windows 10 22h2: 10.0.19045.6456 | Windows 11 22h2: 10.0.22621.6060 | Windows 11 23h2: 10.0.22631.6060 | Windows 11 24h2: 10.0.26100.6899 | Windows

  1. Check current Windows version by running 'winver' or 'systeminfo' to confirm which version is installed
  2. Open Settings > Update & Security > Windows Update and check for updates
  3. Alternatively, navigate to Microsoft Update Catalog (catalog.update.microsoft.com) and search for the specific KB (check msrc.microsoft.com for the KB number associated with CVE-2025-50175)
  4. Download and install the appropriate security update for your Windows version
  5. Restart the system when prompted
  6. Verify the update was installed by checking Windows Update history or running 'winver' to confirm the version matches or exceeds the fixed version for your release
Caveat Standard Windows security update - minimal risk; may require restart

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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