dbcve.org
365 CopilotApplication · Microsoft

CVE-2026-24285

HIGH · 7.0 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
72/100
Remediation priority · Elevated
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 Windows Win32K 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

Use-after-free vulnerability in Windows Win32K kernel-mode graphics subsystem allows a locally authorized attacker to manipulate freed memory objects and elevate privileges to SYSTEM level.

MitigationApply Microsoft security patches for Win32K when released; restrict local debugging privileges and monitor for suspicious kernel-mode module loading.

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.19822.20000
Windows 10 1607Operating system
Affected:< 10.0.14393.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979

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

CVSS:3.1/AV:L/AC:H/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"`. Alternatively, run `ver` in cmd or check Settings > System > About.
    Affected if The displayed version falls within any of these vulnerable ranges: Windows 10 1607 < 10.0.14393.8957, Windows 10 1809 < 10.0.17763.8511, Windows 10 21h2 < 10.0.19044.7058, Windows 10 22h2 < 10.0.19045.7058, Windows 11 23h2 < 10.0.22631.6783, Windows 11 24h2 < 10.0.26100.7979, or Windows 11 25h2 < 10
  2. Verify Win32K kernel driver version
    Open Command Prompt as Administrator and run: `driverquery /v | findstr win32k` or check file properties of C:\Windows\System32\win32k.sys
    Affected if The win32k.sys version is lower than the version corresponding to the patched build for your Windows release, indicating the system lacks the security update.
  3. Confirm local administrator or debugging privileges exist
    Run `whoami /all` and look for SeDebugPrivilege or check if the current user is a member of Administrators or Backup Operators groups.
    Affected if The user account has elevated privileges (local administrator, debug privileges, or backup operator) which are required for a locally authorized attacker to exploit this Win32K use-after-free flaw.
  4. Check Microsoft 365 Copilot version if installed
    Open any Office application (e.g., Word), go to File > Account, and view the version number under "About [App]".
    Affected if Microsoft 365 Copilot is installed and the version is below 16.0.19822.20000.

You are affected if your Windows build number or win32k.sys version is below the patched thresholds for your specific Windows release, and your account has elevated local privileges that could enable exploitation of the Win32K use-after-free vulnerability.

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.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply Microsoft security patches for Win32K when released; restrict local debugging privileges and monitor for suspicious kernel-mode module loading.

Recommended fix High confidence

Windows Security Update (KB patch) for respective build - install the monthly cumulative update containing the CVE-2026-24285 fix

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine which Windows 10 or 11 release channel your system is on (e.g., 21h2, 22h2, 23h2, 24h2, 25h2)
  3. For Windows 10 1607 systems: upgrade to build 10.0.14393.8957 or later
  4. For Windows 10 1809 systems: upgrade to build 10.0.17763.8511 or later
  5. For Windows 10 21h2 systems: upgrade to build 10.0.19044.7058 or later
  6. For Windows 10 22h2 systems: upgrade to build 10.0.19045.7058 or later
  7. For Windows 11 23h2 systems: upgrade to build 10.0.22631.6783 or later
  8. For Windows 11 24h2 systems: upgrade to build 10.0.26100.7979 or later
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for business-critical applications

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-2026-24285 — 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-2026-24285 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