CVE-2026-40369: Windows Kernel ExpGetProcessInformation Local Privilege Escalation
- Vendor
- Microsoft Corporation
CVE-2026-40369 is an untrusted pointer dereference vulnerability in the Windows Kernel's ExpGetProcessInformation routine. When NtQuerySystemInformation processes SystemProcessInformationExtension requests (information class 253) with a zero-length output buffer, ProbeForWrite performs no validation. The routine subsequently continues processing despite detecting insufficient buffer length and updates memory through the attacker-supplied pointer. This yields a constrained kernel-write primitive that increments three consecutive DWORDs using system-wide process, thread, and handle counts. An authorized local attacker can exploit the flaw to elevate privileges. Windows 11 versions 24H2 and 25H2 are identified as affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can grant specific limited SYSTEM privileges. Further exploitation of the kernel-memory modification primitive can enable kernel reads, KASLR bypass, token privilege manipulation, and eventual SYSTEM-level execution. The vulnerable syscall is reachable from browser renderer sandboxes, making the flaw usable in sandbox-escape chains. Targeting invalid or unmapped kernel memory can cause a PAGE_FAULT_IN_NONPAGED_AREA bugcheck and system-wide denial of service. Microsoft rates the vulnerability Important, with a CVSS v3.1 base score of 7.8.
Mitigation
If you can’t patch tonight, do this now.
No vendor-documented workaround is identified. As supplementary detection measures, monitor anomalous NtQuerySystemInformation usage and suspicious kernel-memory modification activity. Monitoring does not prevent exploitation and is not a substitute for applying the security update.
Remediation
Patch, then assume compromise.
Install Microsoft's security update addressing CVE-2026-40369, released in the May 12, 2026 Patch Tuesday updates, or a subsequent cumulative update containing the fix. Select the update applicable to the installed Windows release; specific fixed builds and update identifiers for this CVE are not available here.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 3 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-40369 exploited in the wild?
- As of Nov 3, 2026, Mallory has no reports of CVE-2026-40369 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-40369?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2026-40369, the earliest disclosed May 13, 2026.
- Is there a patch for CVE-2026-40369?
- Install Microsoft's security update addressing CVE-2026-40369, released in the May 12, 2026 Patch Tuesday updates, or a subsequent cumulative update containing the fix. Select the update applicable to the installed Windows release; specific fixed builds and update identifiers for this CVE are not available here.
- What products are affected by CVE-2026-40369?
- Microsoft Corporation Windows, Microsoft Corporation Windows 11 24h2, Microsoft Corporation Windows 11 25h2, Microsoft Corporation Windows 11 26h1, Microsoft Corporation Windows 11 2h2, and 1 more.
- How severe is CVE-2026-40369?
- CVE-2026-40369 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 4.7% (92nd percentile) as of Nov 3, 2026.
Recent activity
78 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.