dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-26666

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.17763.7136 / 10.0.19044.5737 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 Windows Media 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 vulnerability in Windows Media parsing component allows a locally authenticated attacker with authorized access to execute arbitrary code by triggering the overflow through specially crafted media content.

MitigationApply Microsoft security updates for Windows Media once released. Prioritize patching systems where users process untrusted media files. Verify media functionality remains intact post-patch.

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.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775
Windows Server 2019Operating system
Affected:< 10.0.17763.7136
Windows Server 2022Operating system
Affected:< 10.0.20348.3453

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. Identify Windows version and build number
    Run 'winver' from Start menu or execute 'systeminfo' in Command Prompt and note the OS Version and Build Number
    Affected if The build number is lower than the threshold for your Windows release (17763.7136 for 10 1809/Server 2019, 19044.5737 for 10 21h2, 19045.5737 for 10 22h2, 22621.5189 for 11 22h2, 22631.5189 for 11 23h2, 26100.3775 for 11 24h2, or 20348.3453 for Server 2022)
  2. Verify Windows Media Player component is present
    Open Control Panel > Programs and Features > Turn Windows features on or off, or run 'Get-WindowsOptionalFeature -Online -FeatureName *Media*' in PowerShell to list media-related features
    Affected if Windows Media Player or Windows Media Feature Pack is enabled, as the vulnerability exists in the media parsing component
  3. Check Windows Media Foundation service status
    Run 'Get-Service -Name MediaFoundation' or check Services.msc for 'Windows Media Foundation' service
    Affected if The Windows Media Foundation service exists and is running, as this is the parsing component containing the vulnerability

You are affected if your Windows build number is below the version threshold for your specific Windows release and Windows Media components are enabled 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.7136 / 10.0.19044.5737 / 10.0.19045.5737 or later
Fixed in 10.0.17763.713610.0.19044.573710.0.19045.5737
Interim mitigation

Apply Microsoft security updates for Windows Media once released. Prioritize patching systems where users process untrusted media files. Verify media functionality remains intact post-patch.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.7136+ | Windows 10 21h2: 10.0.19044.5737+ | Windows 10 22h2: 10.0.19045.5737+ | Windows 11 22h2: 10.0.22621.5189+ | Windows 11 23h2: 10.0.22631.5189+ | Windows 11 24h2: 10.0.26100.3775+ | Windows Server 2019: 10.0.17763.7136+ | Windows Server 2022: 10.0.20348.3453+

  1. Identify the current Windows version by running 'winver' or 'systeminfo' to confirm which affected version is installed
  2. For Windows 10 (1809): Install KB5055523 (10.0.17763.7136) or later via Windows Update or Microsoft Update Catalog
  3. For Windows 10 (21h2): Install KB5055537 (10.0.19044.5737) or later via Windows Update or Microsoft Update Catalog
  4. For Windows 10 (22h2): Install KB5055525 (10.0.19045.5737) or later via Windows Update or Microsoft Update Catalog
  5. For Windows 11 (22h2): Install KB5055519 (10.0.22621.5189) or later via Windows Update or Microsoft Update Catalog
  6. For Windows 11 (23h2): Install KB5055520 (10.0.22631.5189) or later via Windows Update or Microsoft Update Catalog
  7. For Windows 11 (24h2): Install KB5055527 (10.0.26100.3775) or later via Windows Update or Microsoft Update Catalog
  8. For Windows Server 2019: Install KB5055523 (10.0.17763.7136) or later via Windows Update or WSUS
Caveat Standard Windows cumulative update risks apply; test in non-production environment first if possible

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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