CVE-2025-48806
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 · uneditedUse after free 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 confidenceA use-after-free vulnerability in Microsoft MPEG-2 Video Extension allows a local authenticated attacker to achieve code execution by exploiting memory that is accessed after being freed. The vulnerability affects the video decoding component and can be triggered through specially crafted MPEG-2 video files or streams.
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< 10.0.10240.21073< 10.0.14393.8246< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify MPEG-2 Video Extension is installedOpen PowerShell and run: Get-AppxPackage -Name *MPEG2Video* to find the Microsoft MPEG-2 Video Extension package. If no result is returned, the component is not installed.Affected if The extension package is not found in the installed apps list.
-
Retrieve the installed versionIn the same PowerShell output from Get-AppxPackage, note the Version field for the MPEG-2 Video Extension package.Affected if The version number is lower than the thresholds: 10.0.10240.21073 (Win10 1507), 10.0.14393.8246 (Win10 1607), 10.0.17763.7558 (Win10 1809), 10.0.19044.6093 (Win10 21h2), 10.0.19045.6093 (Win10 22h2), 10.0.22621.5624 (Win11 22h2), 10.0.22631.5624 (Win11 23h2), or 10.0.26100.4652 (Win11 24h2).
-
Confirm Windows version for accurate version matchingRun 'winver' in the Run dialog or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt to identify your exact Windows release and build.Affected if The Windows build combined with the MPEG-2 extension version falls below the corresponding version threshold for that Windows release.
-
Check if MPEG-2 video playback capability is presentAttempt to play an MPEG-2 video file (.mpg, .mpeg, .m2v) using the Movies & TV app or any application that uses Windows media foundations. The extension activates when such content is played.Affected if MPEG-2 videos can be played, indicating the vulnerable component is loaded and actively used by the system.
Your environment is affected if the Microsoft MPEG-2 Video Extension is installed and its version is below the threshold corresponding to your Windows version, especially if you can play MPEG-2 video content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2107310.0.14393.824610.0.17763.7558
Apply the relevant Microsoft security update for the MPEG-2 Video Extension via Windows Update or Microsoft Update Catalog. Verify the patch deployment and test video playback functionality post-update.
Upgrade to a Windows build number at or above the threshold for your Windows version (e.g., Windows 10 22h2: >=10.0.19045.6093, Windows 11 23h2: >=10.0.22631.5624)
- Open Windows Settings and navigate to Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Verify the update is installed by going to Settings > System > About and checking the OS build number matches or exceeds the fixed version for your Windows edition
- For Windows 10 1507: ensure build >= 10.0.10240.21073
- For Windows 10 1607: ensure build >= 10.0.14393.8246
- For Windows 10 1809: ensure build >= 10.0.17763.7558
- For Windows 10 21h2: ensure build >= 10.0.19044.6093
- For Windows 10 22h2: ensure build >= 10.0.19045.6093
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48806 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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