dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2025-49682

HIGH · 7.3 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.19044.6093 / 10.0.19045.6093 or later.
See remediation →
73/100
Remediation priority · Elevated

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

Use-after-free vulnerability in Windows Media component allows a locally authenticated attacker to elevate privileges to higher permissions by exploiting memory corruption when the vulnerable code accesses freed memory.

MitigationApply available Windows security updates through Windows Update or enterprise patch management systems to address the vulnerability in the Windows Media component.

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 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
Windows Server 2022Operating system
Affected:< 10.0.20348.3932
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1732
Windows Server 2025Operating 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the full build number
    Affected if The build number is lower than the affected version for your Windows release (19044, 19045, 22621, 22631, 26100, 20348, 25398)
  2. Confirm Windows release version
    Run 'winver' to identify if you are on Windows 10 21h2, 10 22h2, Windows 11 22h2/23h2/24h2, Server 2022, Server 2022 23h2, or Server 2025
    Affected if Your specific release matches one of the affected versions and is below the corresponding build threshold
  3. Verify Windows Media component presence
    Check if Windows Media Player or Media Foundation is enabled: Run 'Get-WindowsOptionalFeature -Online -FeatureName *Media*' or inspect %SystemRoot%\System32\mf.dll existence
    Affected if The Windows Media component (Media Foundation mf.dll or Windows Media Player) is installed on the system

You are affected if your Windows build number is below the threshold for your specific Windows release and the Windows 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.19044.6093 / 10.0.19045.6093 / 10.0.20348.3932 or later
Fixed in 10.0.19044.609310.0.19045.609310.0.20348.3932
Interim mitigation

Apply available Windows security updates through Windows Update or enterprise patch management systems to address the vulnerability in the Windows Media component.

Recommended fix High confidence

Upgrade to the latest cumulative update for your Windows version: Windows 10 21h2 (build 10.0.19044.6093+), Windows 10 22h2 (build 10.0.19045.6093+), Windows 11 22h2 (build 10.0.22621.5624+), Windows 11 23h2 (build 10.0.22631.5624+), Windows 11 24h2 (build 10.0.26100.4652+), Windows Server 2022 (bui

  1. 1. Identify the current Windows version by running `winver` or `systeminfo` in Command Prompt
  2. 2. Determine which Windows release (21h2, 22h2, 23h2, 24h2, Server 2022, Server 2022 23h2, or Server 2025) matches your installed version
  3. 3. Open Windows Settings > Update & Security > Windows Update
  4. 4. Check for updates and install all available cumulative updates
  5. 5. Alternatively, download the specific cumulative update KB from Microsoft Update Catalog matching your Windows version and build number
  6. 6. Restart the system after updates are installed
  7. 7. Verify the installed version matches or exceeds the fixed build number for your release (e.g., Windows 10 22h2 should be 10.0.19045.6093 or later)
Caveat Standard Windows cumulative update applies; no breaking changes expected for this security patch

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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