dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62458

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8688 / 10.0.17763.8146 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 Win32K - GRFX 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 heap-based buffer overflow vulnerability exists in the Windows Win32K graphics subsystem (GRFX component). This local privilege escalation flaw allows an authorized attacker to exploit the overflow and gain elevated SYSTEM-level privileges on the affected Windows system.

MitigationApply Microsoft security updates for CVE-2025-62458 immediately. Until a patch is available, minimize the attack surface by restricting local user permissions and monitoring for suspicious processes attempting to interact with Win32K syscalls.

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 1607Operating system
Affected:< 10.0.14393.8688
Windows 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows Server 2008Operating system
Affected:= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8688

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 use 'systeminfo' in Command Prompt, or run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayerVersion' in PowerShell
    Affected if The detected Windows version and build number fall within any of the affected ranges: Windows 10 1607 < build 14393.8688, Windows 10 1809 < build 17763.8146, Windows 10 21h2 < build 19044.6691, Windows 10 22h2 < build 19045.6691, Windows 11 23h2 < build 22631.6345, Windows Server 2016 < build 14393.
  2. Check if Win32K.sys is present
    Verify the file exists at C:\Windows\System32\win32k.sys
    Affected if The file exists (this confirms the Win32K graphics subsystem component is present, which contains the vulnerable GRFX component)
  3. Confirm system is unpatched for this CVE
    Check installed security updates by running 'Get-HotFix | Where-Object {$_.Description -like "Security Update"}' in PowerShell or view the update history in Settings > Windows Update > Update history, looking for the CVE-2025-62458 security update
    Affected if No corresponding security update for CVE-2025-62458 is installed and the Windows version falls within the affected ranges

A system is affected if it runs any Windows version within the specified affected ranges AND lacks the security update that addresses CVE-2025-62458, since this local privilege escalation vulnerability exists in the Win32K graphics subsystem (GRFX component) on unpatched systems.

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.14393.8688 / 10.0.17763.8146 / 10.0.19044.6691 or later
Fixed in 10.0.14393.868810.0.17763.814610.0.19044.6691
Interim mitigation

Apply Microsoft security updates for CVE-2025-62458 immediately. Until a patch is available, minimize the attack surface by restricting local user permissions and monitoring for suspicious processes attempting to interact with Win32K syscalls.

Recommended fix High confidence

Upgrade to the May 2025 Windows Security Update (or later) that addresses CVE-2025-62458 - specific KB number varies by OS version; check MSRC for the correct KB for your build

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Download and install the appropriate Windows Security Update from Microsoft Update Catalog matching your OS version and build (e.g., KB506XXXX for May 2025 Patch Tuesday)
  3. Restart the system after applying the update
  4. Verify the installation by checking the new build number matches or exceeds: 10.0.14393.8688 (1607/Server 2016), 10.0.17763.8146 (1809), 10.0.19044.6691 (21h2), 10.0.19045.6691 (22h2), or 10.0.22631.6345 (11 23h2)
  5. For Windows Server 2008 R2 and Server 2012, contact Microsoft for extended support options as these are end-of-life
Caveat Standard Windows update; ensure backups and compatibility testing for critical line-of-business applications before deployment

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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