dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-27467

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
Use after free in Windows Digital Media allows an authorized attacker to elevate privileges 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 use-after-free vulnerability in Windows Digital Media enables a locally authorized attacker to execute code with elevated privileges by freeing memory that the application still references.

MitigationApply the Microsoft security update for this vulnerability via Windows Update or enterprise patch management systems.

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 2022 23h2Operating system
Affected:< 10.0.25398.1551

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 the Run dialog or 'systeminfo' from command prompt and record the OS build number displayed
    Affected if The displayed build number is lower than the threshold for your specific Windows edition in the affected versions list
  2. Determine the exact Windows edition
    From systeminfo output, identify whether you are running Windows 10 version 1809, 21h2, or 22h2; Windows 11 version 22h2, 23h2, or 24h2; Windows Server 2019; or Windows Server 2022 23h2
    Affected if Running any of the editions listed in the affected products
  3. Compare your build against affected thresholds
    Cross-reference your detected build number against the following thresholds: Windows 10 1809 and Server 2019: < 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 2022 23h2: < 10.0.25398.1551
    Affected if Your installed build number is below the corresponding threshold for your detected Windows edition

If your Windows build number falls below the threshold for your specific Windows edition, the system is potentially affected by this use-after-free vulnerability in Windows Digital Media.

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 the Microsoft security update for this vulnerability via Windows Update or enterprise patch management systems.

Recommended fix High confidence

Apply the appropriate Microsoft security update for your specific Windows version to reach the fixed build numbers listed (e.g., Windows 10 22h2: 10.0.19045.5737+, Windows 11 23h2: 10.0.22631.5189+, etc.)

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version and build you are running from the list of affected products
  3. Navigate to Windows Update settings and check for updates, or manually download the appropriate security update from the Microsoft Update Catalog for your specific Windows version
  4. Install the corresponding security update: For Windows 10 1809/Windows Server 2019, install build 10.0.17763.7136 or later; For Windows 10 21h2, install build 10.0.19044.5737 or later; For Windows 10 22h2, install build 10.0.19045.5737 or later; For Windows 11 22h2, install build 10.0.22621.5189 or later; For Windows 11 23h2, install build 10.0.22631.5189 or later; For Windows 11 24h2, install bui
  5. Restart the system after applying the update
  6. Verify the update was successfully installed by checking the installed updates via 'appwiz.cpl' or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows security update with no expected breaking changes; as a routine patch, verify compatibility with line-of-business applications after reboot

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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