CVE-2026-20805AnalysisPublished 15 Jan 2026

Microsoft Desktop Window Manager Zero-Day Vulnerability (CVE-2026-20805) Actively Exploited; Urgent Patch Released

Source Community Curated

Authoritative record:CVE-2026-20805· Medium 5.5

Exploited in the wild · KEV due 3 Feb 2026 : block it and hunt for it in your logs now.

Data as of 15 Jan 2026, 15:22 UTC

CVSS base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 3 Feb 2026 US federal agencies must patch by this date; a sensible deadline for everyone else.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV the same day as disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by microsoft
2025-12-0305:54Z, 41 days before disclosure
CVE published
on cve.org
2026-01-1317:56Z, t = 0
In Threat Radar
record ingested
2026-01-1318:11Z, 16 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2026-01-13, the same day as disclosure
KEV remediation due
US federal deadline
2026-02-03, 21 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
MicrosoftWindows 10 Version 1607	Affected >=10.0.14393.0 <10.0.14393.8783	Fixed in 10.0.14393.8783
MicrosoftWindows 10 Version 1809	Affected >=10.0.17763.0 <10.0.17763.8276	Fixed in 10.0.17763.8276
MicrosoftWindows 10 Version 21H2	Affected >=10.0.19044.0 <10.0.19044.6809	Fixed in 10.0.19044.6809
MicrosoftWindows 10 Version 22H2	Affected >=10.0.19045.0 <10.0.19045.6809	Fixed in 10.0.19045.6809
MicrosoftWindows 11 version 23H2	Affected >=10.0.22631.0 <10.0.22631.6491	Fixed in 10.0.22631.6491
MicrosoftWindows 11 Version 23H2	Affected >=10.0.22631.0 <10.0.22631.6491	Fixed in 10.0.22631.6491
MicrosoftWindows 11 Version 24H2	Affected >=10.0.26100.0 <10.0.26100.7623	Fixed in 10.0.26100.7623
MicrosoftWindows 11 Version 25H2	Affected >=10.0.26200.0 <10.0.26200.7623	Fixed in 10.0.26200.7623
MicrosoftWindows Server 2012	Affected >=6.2.9200.0 <6.2.9200.25868	Fixed in 6.2.9200.25868
MicrosoftWindows Server 2012 (Server Core installation)	Affected >=6.2.9200.0 <6.2.9200.25868	Fixed in 6.2.9200.25868
MicrosoftWindows Server 2012 R2	Affected >=6.3.9600.0 <6.3.9600.22968	Fixed in 6.3.9600.22968
MicrosoftWindows Server 2012 R2 (Server Core installation)	Affected >=6.3.9600.0 <6.3.9600.22968	Fixed in 6.3.9600.22968
MicrosoftWindows Server 2016	Affected >=10.0.14393.0 <10.0.14393.8783	Fixed in 10.0.14393.8783
MicrosoftWindows Server 2016 (Server Core installation)	Affected >=10.0.14393.0 <10.0.14393.8783	Fixed in 10.0.14393.8783
MicrosoftWindows Server 2019	Affected >=10.0.17763.0 <10.0.17763.8276	Fixed in 10.0.17763.8276
MicrosoftWindows Server 2019 (Server Core installation)	Affected >=10.0.17763.0 <10.0.17763.8276	Fixed in 10.0.17763.8276
MicrosoftWindows Server 2022	Affected >=10.0.20348.0 <10.0.20348.4648	Fixed in 10.0.20348.4648
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)	Affected >=10.0.25398.0 <10.0.25398.2092	Fixed in 10.0.25398.2092
MicrosoftWindows Server 2025	Affected >=10.0.26100.0 <10.0.26100.32230	Fixed in 10.0.26100.32230
MicrosoftWindows Server 2025 (Server Core installation)	Affected >=10.0.26100.0 <10.0.26100.32230	Fixed in 10.0.26100.32230

Description

This article details a recently patched critical zero-day vulnerability (CVE-2026-20805) in Microsoft's Desktop Window Manager (DWM) that allows local low-privilege attackers to disclose sensitive memory addresses, aiding privilege escalation. The vulnerability is actively exploited in the wild and affects legacy Windows versions still under extended support. Microsoft has released patches and recommends urgent deployment alongside monitoring and restricting local low-privilege accounts.

Impact

The content provides timely, actionable threat intelligence on a critical zero-day vulnerability with detailed technical context, exploitation status, affected platforms, and mitigation guidance, making it highly relevant for defenders.

Defensive guidance

Defenders should prioritize applying the January 13, 2026 Patch Tuesday updates for affected Windows versions, restrict local low-privilege account access, and monitor DWM processes using EDR tools to detect potential exploitation attempts.

References

cybersecuritynews.com/desktop-window-manager-0-day-vulnerability/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jan 2026, 15:22 UTC

Technical details

References

Community reviews

Related threats