dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29840

HIGH · 8.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Stack-based buffer overflow in Windows Media allows an unauthorized attacker to execute code over a network.

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 stack-based buffer overflow vulnerability exists in Windows Media that allows an unauthenticated attacker to achieve remote code execution by sending specially crafted media content over a network. The overflow occurs on the stack, potentially allowing attacker-controlled code to execute with the privileges of the affected application.

MitigationApply the latest Microsoft security updates for Windows Media. If immediate patching is not possible, consider network segmentation and disabling Windows Media Player or associated codecs to reduce attack surface until the patch can be deployed.

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.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows Server 2016Operating system
Affected:< 10.0.14393.8066

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 version and build number
    Open Command Prompt or PowerShell and run 'winver' to see the Windows version and build, or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get detailed version information
    Affected if The build number is lower than any of these thresholds: 10.0.10240.21014 (Win10 1507), 10.0.14393.8066 (Win10 1607/Server 2016), 10.0.17763.7314 (Win10 1809), 10.0.19044.5854 (Win10 21h2), 10.0.19045.5854 (Win10 22h2), 10.0.22621.5335 (Win11 22h2), or 10.0.22631.5335 (Win11 23h2)
  2. Verify Windows Media Player is installed
    Open Control Panel > Programs and Features > Turn Windows features on or off, or check the registry key 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponents\WMP' to see if Windows Media Player is present
    Affected if Windows Media Player is installed and enabled on the system
  3. Check for legacy Windows Media components
    Check for the presence of media-related DLLs in system directories (such as wmpeffects.dll, wmp.dll, or mf.dll in System32) or use PowerShell 'Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponents\WMP"' to query component status
    Affected if Any Windows Media Player DLLs or components are present on the system

You are affected if your Windows build number is below the thresholds listed AND Windows Media Player or related media components are installed on your 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.10240.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the latest Microsoft security updates for Windows Media. If immediate patching is not possible, consider network segmentation and disabling Windows Media Player or associated codecs to reduce attack surface until the patch can be deployed.

Recommended fix High confidence
  1. Check the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update (or equivalent)
  3. Click 'Check for updates' to fetch the latest security patches
  4. Locate the security update that addresses CVE-2025-29840 (typically included in the monthly cumulative update)
  5. Review the update details and click 'Download' or 'Install' if not set to auto-download
  6. After installation completes, restart the computer when prompted
  7. Verify the installed version matches or exceeds the fixed version for your Windows release (e.g., 10.0.19045.5854 for Windows 10 22h2)

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

Fix this in Windows 10 1507 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-29840 — 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-29840 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