dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-49708

CRITICAL · 9.9 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 Microsoft Graphics Component allows an authorized attacker to elevate privileges over a network.

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 (UAF) vulnerability in a Microsoft Graphics Component enables an authenticated attacker to elevate privileges, potentially allowing execution with higher system permissions.

MitigationApply Microsoft security updates immediately upon release; prioritize patching systems exposed to network attack vectors given the critical CVSS score and privilege escalation capability.

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.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2019Operating system
Affected:< 10.0.17763.7919

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the full build number including the revision (e.g., 10.0.19045.6456)
    Affected if The reported build number falls below any of the threshold versions listed for your Windows release (10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, 11 24h2, 11 25h2, or Server 2019)
  2. Identify Windows release version
    Run 'winver' or check Settings > System > About to confirm whether you are on Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 22h2, 23h2, 24h2, 25h2, or Windows Server 2019
    Affected if Your specific Windows release matches any of the affected products listed in the CVE
  3. Confirm graphics component is present
    The vulnerability exists in a Microsoft Graphics Component that ships with affected Windows versions; verify the Graphics driver is loaded by running 'driverquery | findstr -i video' or checking Device Manager for display adapters
    Affected if A graphics adapter driver is present and loaded, which is the default configuration for most Windows systems

You are affected if your Windows version matches any of the listed releases and your build number is below the specified threshold for that release.

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.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply Microsoft security updates immediately upon release; prioritize patching systems exposed to network attack vectors given the critical CVSS score and privilege escalation capability.

Recommended fix High confidence

Windows 10 1809: build 10.0.17763.7919 | Windows 10 21h2: build 10.0.19044.6456 | Windows 10 22h2: build 10.0.19045.6456 | Windows 11 22h2: build 10.0.22621.6060 | Windows 11 23h2: build 10.0.22631.6061 or later | Windows 11 24h2: build 10.0.26100.6899 | Windows 11 25h2: build 10.0.26200.6899 | Wind

  1. 1. Identify the current Windows version by running `winver` or checking Settings > System > About
  2. 2. Determine the specific Windows 10 or 11 version and build number from the affected versions list
  3. 3. Open Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest security update
  5. 5. For enterprise deployments, use Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager to deploy the appropriate security update (refer to Microsoft Security Guide MSRC for the specific KB article)
  6. 6. After installation, restart the system to apply the updates
  7. 7. Verify the fix by running `winver` and confirming the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update; no expected breaking changes for this privilege escalation patch

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 / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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