dbcve.org
365 CopilotApplication · Microsoft

CVE-2025-60724

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Microsoft Graphics Component allows an unauthorized attacker to execute code 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

Heap-based buffer overflow vulnerability in a Microsoft graphics component allows an unauthenticated remote attacker to execute arbitrary code. The flaw exists in memory handling within the graphics subsystem.

MitigationApply Microsoft security updates immediately upon release. Until then, minimize network exposure of affected systems and implement defense-in-depth controls.

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.19426.20044
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024
Windows 10 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092

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

CVSS:3.1/AV:N/AC:L/PR:N/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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows 10 or 11 build
    Affected if The build number falls within the affected ranges: Windows 10 1607 < 14393.8594, 1809 < 17763.8027, 21h2 < 19044.6575, 22h2 < 19045.6575, Windows 11 23h2 < 22631.6199, or Windows 11 24h2 < 26100.7092
  2. Check Windows build version
    Run 'winver' or 'ver' command and compare the build number against the KB/field or use 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
    Affected if The displayed build version is lower than the threshold for your Windows release channel
  3. Identify Microsoft Office version
    Open Word/Excel/PowerPoint, go to File > Account > About [App], or run 'winword /?' and check the displayed version number
    Affected if The Office version is 2021 or 2024 Long Term Servicing Channel and falls within the affected range
  4. Check Microsoft 365 Copilot version
    Open the Copilot app, navigate to Settings > About, or check via Apps & Features in Windows Settings for the Copilot package version
    Affected if The Copilot version is below 16.0.19426.20044
  5. Verify graphics subsystem is active
    Check that graphics-related services are running: 'Get-Service' for 'Display' and 'Dwm.exe' (Desktop Window Manager) process is active via Task Manager
    Affected if The graphics subsystem components are loaded and running on an affected Windows version
  6. Confirm vulnerability in graphics component
    Review installed Windows updates: run 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security updates
    Affected if No recent security updates addressing CVE-2025-60724 are installed on the affected Windows or Office product

Your environment is affected if you are running any of the specified Windows 10/11 builds or Office/Copilot versions below the threshold versions listed in the affected ranges, and the graphics subsystem is active.

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.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply Microsoft security updates immediately upon release. Until then, minimize network exposure of affected systems and implement defense-in-depth controls.

Recommended fix High confidence

Windows 10 1607: >= 10.0.14393.8594 | Windows 10 1809: >= 10.0.17763.8027 | Windows 10 21h2: >= 10.0.19044.6575 | Windows 10 22h2: >= 10.0.19045.6575 | Windows 11 23h2: >= 10.0.22631.6199 | Windows 11 24h2: >= 10.0.26100.7092 | Office LTSC 2021/2024: apply security update | Microsoft 365 Copilot: >=

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to install the latest Microsoft security update containing the fix
  3. Alternatively, manually install the applicable Microsoft Security Update for this vulnerability (refer to Microsoft Security Bulletin for KB number)
  4. For Office products: Open any Office application, go to File > Account > Update Options > Update Now
  5. Verify the installed version matches or exceeds the fixed version for your product
Caveat Security updates typically have minimal breaking changes; test in non-production environment before broad deployment

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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