dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-48805

HIGH · 7.8 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 →
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
Heap-based buffer overflow in Microsoft MPEG-2 Video Extension allows an authorized attacker to execute code 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

Heap-based buffer overflow in Microsoft MPEG-2 Video Extension enables a local attacker to execute arbitrary code by exploiting memory corruption in the video processing component.

MitigationApply Microsoft security updates for the MPEG-2 Video Extension once available; until then, restrict local access and monitor for unusual video file processing 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 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
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 10 build version
    Open Settings > System > About and look at the 'Build' number, or run 'winver' command and note the full build version (e.g., 10.0.19045.6093)
    Affected if Build number is lower than the threshold for your Windows 10 release: 1507 (<10.0.10240.21073), 1607 (<10.0.14393.8246), 1809 (<10.0.17763.7558), 21h2 (<10.0.19044.6093), or 22h2 (<10.0.19045.6093)
  2. Check Windows 11 build version
    Open Settings > System > About and look at the 'Build' number, or run 'winver' command and note the full build version (e.g., 10.0.22631.5624)
    Affected if Build number is lower than the threshold for your Windows 11 release: 22h2 (<10.0.22621.5624), 23h2 (<10.0.22631.5624), or 24h2 (<10.0.26100.4652)
  3. Verify MPEG-2 Video Extension is installed
    Open Settings > Apps > Optional Features and search for 'MPEG-2', or run 'Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*MPEG*"}' in PowerShell
    Affected if The MPEG-2 Video Extension feature is listed as installed or enabled on the system

Your system is affected if it runs a Windows version with a build number below the threshold for its release AND has the MPEG-2 Video Extension installed or enabled.

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 Microsoft security updates for the MPEG-2 Video Extension once available; until then, restrict local access and monitor for unusual video file processing activity.

Recommended fix High confidence

Install the corresponding Windows security update from Microsoft's security bulletin (search CVE-2025-48805 on msrc.microsoft.com) that addresses the Microsoft MPEG-2 Video Extension vulnerability

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Windows Update (Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install all available updates
  4. Ensure the Microsoft MPEG-2 Video Extension receives the security update
  5. After updating, verify the version of Windows meets or exceeds: 10.0.10240.21073 (1507), 10.0.14393.8246 (1607), 10.0.17763.7558 (1809), 10.0.19044.6093 (21h2), 10.0.19045.6093 (22h2), 10.0.22621.5624 (11 22h2), 10.0.22631.5624 (11 23h2), or 10.0.26100.4652 (11 24h2)
  6. Alternatively, manually download the security update from the Microsoft Update Catalog or use WSUS for enterprise deployments
Caveat None typically expected for security updates; standard Windows Update process handles dependencies

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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