CVE-2026-34336

Windows DWM Core Library Elevation of Privilege Vulnerability

HIGH
7.8
CVSS Score
Published: May 12, 2026 at 04:59 PM UTC
Updated: August 10, 2026 at 03:39 PM UTC
14 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows 10 1809

Using Windows 10 Version 1607 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1607 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Buffer over-read in Windows DWM Core Library allows an authorized attacker to disclose information locally.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.14393.914010.0.14393.0 ≤ v < 10.0.14393.914010.0.14393.0
Affected range stops below 10.0.14393.9140, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.875510.0.17763.0 ≤ v < 10.0.17763.875510.0.17763.0
Affected range stops below 10.0.17763.8755, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.729110.0.19044.0 ≤ v < 10.0.19044.729110.0.19044.0
Affected range stops below 10.0.19044.7291, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.729110.0.19045.0 ≤ v < 10.0.19045.741710.0.19045.0
Affected range stops below 10.0.19045.7291, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19045.7417, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.707910.0.22631.0 ≤ v < 10.0.22631.707910.0.22631.0 ≤ v < 10.0.22631.721910.0.22631.0
Affected range stops below 10.0.22631.7079, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.22631.7219, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.839010.0.26100.0 ≤ v < 10.0.26100.845710.0.26100.0
Affected range stops below 10.0.26100.8390, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.26100.8457, so it looks safe — our inference, not a vendor statement
v < 10.0.26200.839010.0.26200.0 ≤ v < 10.0.26200.845710.0.26200.0
Affected range stops below 10.0.26200.8390, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.26200.8457, so it looks safe — our inference, not a vendor statement
v < 10.0.28000.211310.0.28000.0 ≤ v < 10.0.28000.211310.0.28000.0
Affected range stops below 10.0.28000.2113, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.914010.0.14393.0 ≤ v < 10.0.14393.914010.0.14393.0
Affected range stops below 10.0.14393.9140, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.875510.0.17763.0 ≤ v < 10.0.17763.875510.0.17763.0
Affected range stops below 10.0.17763.8755, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-126CWE-122

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card