dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49742

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 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
Integer overflow or wraparound in Microsoft Graphics Component 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

Integer overflow in Microsoft Graphics Component allows a local authorized attacker to execute code through arithmetic wraparound, typically leading to heap or stack memory corruption that can be leveraged for arbitrary code execution.

MitigationApply Microsoft security updates for affected Windows components; verify through asset inventory which systems contain the vulnerable graphics component.

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 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build
    Affected if The displayed build number falls below any of these thresholds: 10240.21073 (Win10 1507), 14393.8246 (Win10 1607), 17763.7558 (Win10 1809), 19044.6093 (Win10 21h2), 19045.6093 (Win10 22h2), 22621.5624 (Win11 22h2), 22631.5624 (Win11 23h2), 26100.4652 (Win11 24h2)
  2. Confirm graphics component presence
    Check for the presence of vulnerable graphics DLLs (such as figfx.dll, dxgcore.dll, or similar graphics-related system components) in the System32 folder using 'dir %WINDIR%\System32\*.dll | findstr /i "figfx"' or asset inventory tools
    Affected if Graphics component DLLs exist on the system and the Windows build is below the fixed version thresholds
  3. Query installed security updates
    Run 'wmic qfe list' or 'Get-HotFix' in PowerShell to enumerate installed Windows updates
    Affected if No security update corresponding to CVE-2025-49742 is listed among installed hotfixes and the Windows build is within the vulnerable ranges

The system is affected if it runs any Windows 10 or Windows 11 version with a build number lower than the fixed versions listed, and the Microsoft Graphics Component is present.

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.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply Microsoft security updates for affected Windows components; verify through asset inventory which systems contain the vulnerable graphics component.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21073 | Windows 10 1607: 10.0.14393.8246 | Windows 10 1809: 10.0.17763.7558 | Windows 10 21h2: 10.0.19044.6093 | Windows 10 22h2: 10.0.19045.6093 | Windows 11 22h2: 10.0.22621.5624 | Windows 11 23h2: 10.0.22631.5624 | Windows 11 24h2: 10.0.26100.4652

  1. Check the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Confirm the version falls within the affected ranges listed for this CVE
  3. Back up critical data before applying updates as a precaution
  4. Open Windows Update by pressing Win+I and navigating to Windows Update
  5. Click 'Check for updates' and install all available updates
  6. Restart the system when prompted to complete the installation
  7. Verify the installed version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative updates typically have minimal breaking changes; however, verify application compatibility with the specific Windows version if running legacy software

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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