Microsoft Windows DWM Core Library Use-After-Free Vulnerability
Microsoft · Windows
The Windows Desktop Window Manager (DWM) Core Library contains a use-after-free flaw, a memory-safety weakness classified as Use After Free. An attacker who already holds an authorized, low-privilege account on the local system can exploit it to elevate their privileges, with no user interaction required.
Use after free in Windows DWM allows an authorized attacker to elevate privileges locally.
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 3/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.How attackers get in
What they do
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited the day it was disclosed.
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order 2PersistenceTA0003
This vulnerability has been exploited to escalate an attacker's privileges to SYSTEM-level via Microsoft Windows Desktop Window Manager (DWM) Core Library, allowing the attacker to take significant actions such as registry modification.
Privilege EscalationTA0004
Detection
0 rules for this CVE · 129 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2025-30400 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Exploitation for Privilege EscalationT106831 general rules
- Exploiting CVE-2019-1388criticalstable
- Audit CVE Eventcriticaltest
- HackTool - SysmonEOP Executioncriticaltest
- InstallerFileTakeOver LPE CVE-2021-41379 File Create Eventcriticaltest
- Possible Coin Miner CPU Priority Paramcriticaltest
- Potential CVE-2021-41379 Exploitation Attemptcriticaltest
- Potential SystemNightmare Exploitation Attemptcriticaltest
- Sudo Privilege Escalation CVE-2019-14287 - Builtincriticaltest
Modify RegistryT111298 general rules
- FlowCloud Registry Markerscriticaltest
- OceanLotus Registry Activitycriticaltest
- OilRig APT Activitycriticaltest
- OilRig APT Registry Persistencecriticaltest
- OilRig APT Schedule Task Persistence - Securitycriticaltest
- OilRig APT Schedule Task Persistence - Systemcriticaltest
- Registry Entries For Azorult Malwarecriticaltest
- ShimCache Flushhighstable
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 30, 202629 Oct 2026
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- 44 more on OTX