dbcve.org
365 CopilotApplication · Microsoft

CVE-2025-26687

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Win32K - GRFX allows an unauthorized 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 vulnerability in the Windows Win32K graphics subsystem (GRFX) allows an unauthorized attacker to elevate privileges. The vulnerability involves improper memory management in kernel-mode graphics handling, potentially enabling a local attacker to gain elevated system or administrative privileges.

MitigationApply Microsoft security updates for CVE-2025-26687 via Windows Update or manual patch deployment. Prioritize patching systems that handle untrusted content or are exposed to network attack vectors.

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
365 CopilotApplication
Affected:< 16.0.18730.20000
OfficeApplication
Affected:< 16.0.14326.22331
Windows 10 1507Operating system
Affected:< 10.0.10240.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
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

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 build number
    Open Command Prompt and run `winver` or `systeminfo | findstr /B /C:"OS Version"` to display the Windows build number
    Affected if Build number is lower than the affected thresholds for your Windows version (10.0.10240.20978 for 1507, 10.0.14393.7969 for 1607, 10.0.17763.7136 for 1809, 10.0.19044.5737 for 21h2, 10.0.19045.5737 for 22h2, or 10.0.22621.5189 for Windows 11 22h2)
  2. Identify Windows version edition
    Run `winver` or check System Properties to confirm whether you are running Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2
    Affected if Running any of the listed Windows 10 or Windows 11 22h2 versions without the corresponding build patch applied
  3. Verify Win32K graphics subsystem status
    The Win32K graphics subsystem (win32k.sys) is a core Windows kernel component loaded by default on all graphical Windows installations; no configuration check needed - the vulnerability applies if the Windows version falls within affected ranges
    Affected if Windows is running with graphical interface and version is unpatched
  4. Check Microsoft Office version (if installed)
    Open any Office application, go to File > Account > About [App] or run `winword /?` to display the version, or check via Registry: `reg query "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" /v VersionToReport`
    Affected if Office version is below 16.0.14326.22331
  5. Check Microsoft 365 Copilot version (if installed)
    Open any Microsoft 365 application, go to File > Account > About [App] to view the version number
    Affected if Microsoft 365 Copilot version is below 16.0.18730.20000

You are affected if your Windows build number falls below the specified threshold for your Windows version, or if your Microsoft Office/365 version is below the stated patch levels.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply Microsoft security updates for CVE-2025-26687 via Windows Update or manual patch deployment. Prioritize patching systems that handle untrusted content or are exposed to network attack vectors.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20978 or later | Windows 10 1607: 10.0.14393.7969 or later | 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 | Office: 16.0.14326.22331 or later |

  1. Check the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative security update
  4. For Office/365 Copilot: Open any Office application, go to File > Account > Update Options > Update Now
  5. Restart the computer after updates are installed
  6. Verify the update was successful by checking the installed updates in Control Panel > Programs and Features > View installed updates
Caveat Standard Windows cumulative updates typically have minimal breaking changes; verify compatibility with critical line-of-business applications before deployment in enterprise environments

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

Fix this in 365 Copilot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
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,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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