dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-26674

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

A heap-based buffer overflow vulnerability in Windows Media permits a local, authenticated attacker to achieve code execution by overflowing a heap-allocated buffer through specially crafted media content.

MitigationApply Microsoft security updates for affected Windows versions once released; limit local machine access to trusted users only.

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. Check Windows version and build number
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo' and look at 'OS Version' line
    Affected if The displayed build number falls below any of these thresholds: 17763.7136 (Win10 1809/Server 2019), 19044.5737 (Win10 21h2), 19045.5737 (Win10 22h2), 22621.5189 (Win11 22h2), 22631.5189 (Win11 23h2), 26100.3775 (Win11 24h2), or 20348.3453 (Server 2022)
  2. Verify Windows Media component is present
    Check for presence of Windows Media Player: open Settings > Apps > Optional Features, or run 'Get-WindowsOptionalFeature -Online -FeatureName *Media*' in PowerShell
    Affected if Windows Media Player or Windows Media Features are installed on the system
  3. Confirm the specific Windows edition
    Run 'winver' or check System Info to determine if the installed version is Windows 10 1809, 21h2, 22h2, Windows 11 22h2/23h2/24h2, Server 2019, or Server 2022
    Affected if The system runs any of the affected editions listed in the CVE and the build number is below the corresponding threshold

You are affected if your Windows version and build match any of the listed affected products AND your build number is below the specified threshold AND 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.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 affected Windows versions once released; limit local machine access to trusted users only.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.7136 or later | Windows 10 21h2: 10.0.19044.5737 or later | Windows 10 22h2: 10.0.19045.5737 or later | Windows 11 22h2: 10.0.22621.5189 or later | Windows 11 23h2: 10.0.22631.5189 or later | Windows 11 24h2: 10.0.26100.3775 or later | Windows Server 2019: 10.0.17763.7136

  1. Open Windows Settings on the affected system
  2. Navigate to 'Update & Security' > 'Windows Update'
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the update includes the version matching or exceeding: 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
  5. Restart the system after the update is installed
  6. Verify the installed version by running 'winver' or checking System Information
Caveat Standard Windows security update with no expected breaking changes; test in staging if needed for enterprise deployments

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
  • 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-26674 — 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-26674 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