14/11/2026

CVE-2026-95922 in Windows: Local Privilege Escalation via Heap Buffer Overflow

CVE-2026-95922 Windows

Microsoft identifies CVE-2026-95922 as a heap buffer overflow in Windows Graphics Kernel that can let an existing user escalate locally to SYSTEM if a race condition is won. Rated CVSS 7.0 Important, it calls for the applicable update.

CVE-2026-95922 in Windows: Local Privilege Escalation via Heap Buffer Overflow

At a glance

  • CVE-2026-95922 is a heap buffer overflow in Windows Graphics Kernel.
  • An attacker with existing access could escalate local privileges to SYSTEM if exploitation succeeds.
  • Listed Windows branches and Office products have corresponding updates.
  • Prioritize installing the KB or build applicable to each system in the earliest update cycle.
In this article

Microsoft published advisory CVE-2026-95922 on 2026-11-13, describing a local privilege escalation vulnerability in Windows Graphics Kernel. Compare the Microsoft MSRC advisory with the versions and updates installed on your systems.

Overview and technical details

Windows Graphics Kernel is a Windows kernel component that handles operating system graphics functions. CVE-2026-95922 is a heap buffer overflow; successful exploitation could enable local privilege escalation to SYSTEM. Exploitation requires the attacker to have access already and win a race condition.

FieldDetails
Product/componentWindows Graphics Kernel
CVECVE-2026-95922
CWECWE-122: Heap-based Buffer Overflow
CVSS7.0 (Important), CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Publicly DisclosedNo
Exploited in the WildNo
SourceMicrosoft MSRC

Affected systems

The advisory record lists the following Windows versions and Office products with corresponding KBs or update builds. Match each system to its specific version branch and architecture.

Product/versionListed update
Microsoft Office for AndroidBuild 16.0.20625.20014 (KBRelease Notes)
Microsoft Office LTSC for Mac 2021; Microsoft Office LTSC for Mac 2024; Microsoft Office 365 for MacBuild 16.115.26110837 (KBRelease Notes)
Windows Server 2025, including Server Core installationKB5131080, Build 10.0.26100.33822; KB5131077, Build 10.0.26100.33730
Windows 11 Version 26H1, ARM64 and x64KB5132059, Build 10.0.28000.3501
Windows 11 Version 26H2, ARM64 and x64KB5132061, Build 10.0.26300.9974; KB5132043, Build 10.0.26300.9911
Windows 11 Version 24H2, ARM64 and x64KB5132061, Build 10.0.26100.9974; KB5132043, Build 10.0.26100.9911
Windows 11 Version 25H2, ARM64 and x64KB5132061, Build 10.0.26200.9974; KB5132043, Build 10.0.26200.9911
Windows 11 Version 23H2, x64 and ARM64KB5131087, Build 10.0.22631.7711
Windows Server 2022, including Server Core installationKB5131090, Build 10.0.20348.5870
Windows 10 Version 21H2, x64, 32-bit and ARM64KB5131096, Build 10.0.19044.7846
Windows 10 Version 22H2, ARM64, x64 and 32-bitKB5131096, Build 10.0.19045.7846
Windows Server 2019, including Server Core installation; Windows 10 Version 1809, x64 and 32-bitKB5131085, Build 10.0.17763.9487
Windows Server 2016, including Server Core installation; Windows 10 Version 1607, 32-bit and x64KB5131291, Build 10.0.14393.9688

Mechanism and impact

The heap buffer overflow is in Windows Graphics Kernel. An attacker must already have access and win a race condition; successful exploitation could allow local privilege escalation to SYSTEM. The confirmed impact is privilege escalation, not remote exploitation.

Exploitation status

Microsoft records Publicly Disclosed: No and Exploited in the Wild: No. These statuses mean the advisory does not confirm public disclosure or exploitation in the wild.

System checks

  1. Collect the Windows product name, version, and build to identify the branch to compare:

    Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber
  2. Check installed hotfixes, then compare them with the KB applicable to the system version and build:

    Get-HotFix | Select-Object HotFixID, InstalledOn

Remediation and mitigation

  1. Prioritize installing the security update KB applicable to the Windows version in use in the earliest update cycle; compare the KB and build in the affected systems table.

  2. For the listed Office products, apply the update with the corresponding build.

References