dbcve.org
365 CopilotApplication · Microsoft

CVE-2026-25180

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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
Out-of-bounds read in Microsoft Graphics Component allows an unauthorized attacker to disclose information 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

An out-of-bounds read vulnerability exists in a Microsoft Graphics Component that allows a local, unauthorized attacker to read sensitive information from memory. This is a memory safety flaw where the component accesses memory beyond allocated buffers, potentially exposing sensitive data to an unprivileged user.

MitigationApply Microsoft security updates as they become available for the affected Windows graphics components. Maintain current patch levels on all Windows systems to receive vendor fixes.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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
    Run 'winver' from command prompt or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build number
    Affected if The build number falls below any of these thresholds: 14393.8957 (Win10 1607), 17763.8511 (Win10 1809), 19044.7058 (Win10 21h2), 19045.7058 (Win10 22h2), 22631.6783 (Win11 23h2), 26100.7979 (Win11 24h2), 26200.7979 (Win11 25h2)
  2. Check Microsoft 365 Copilot version
    Open PowerShell and run 'Get-AppxPackage -Name *Copilot* | Select-Object Name, Version' to find the installed Copilot package version, or check the version from Add/Remove Programs
    Affected if Microsoft 365 Copilot is installed and its version is below 16.0.19822.20000
  3. Identify graphics component in use
    Check if Windows Graphics components are in use by examining running processes related to graphics (such as dwm.exe, graphics drivers, or related DLLs). Use 'tasklist | findstr -i graphics' or review installed graphics-related Windows components via 'Get-WindowsOptionalFeature -Online | Where-Object {$_.State -eq "Enabled"}'
    Affected if The system uses Windows graphics components (default state for affected Windows versions) and the version check from step 1 or 2 shows the system is below the fixed version thresholds

You are affected if your Windows build number is below the version thresholds listed for your Windows release, or if Microsoft 365 Copilot is installed with a version below 16.0.19822.20000.

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 updates as they become available for the affected Windows graphics components. Maintain current patch levels on all Windows systems to receive vendor fixes.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8957 or later | Windows 10 1809: 10.0.17763.8511 or later | Windows 10 21h2: 10.0.19044.7058 or later | Windows 10 22h2: 10.0.19045.7058 or later | Windows 11 23h2: 10.0.22631.6783 or later | Windows 11 24h2: 10.0.26100.7979 or later | Windows 11 25h2: 10.0.26200.7979 or

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually download the appropriate security update from the Microsoft Update Catalog for your specific Windows version
  5. Restart the system after installing updates to apply the changes
  6. Verify the installed version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply (potential for compatibility issues with older software); ensure critical data is backed up before updating

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

Fix this in 365 Copilot Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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