CVE-2025-30400
CVE-2025-30400 is a security flaw in Microsoft Windows, Microsoft’s operating system for PCs and servers. Someone who already has a foothold can use Microsoft Windows to take full control of the machine. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 13 May 2025.[1]
Microsoft Windows is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Fixed in version 10.0.17763.7314, 10.0.19044.5854, 10.0.19045.5854 and 10.0.22621.5335 and others.
Description
CISA calls it a DWM core library use-after-free in Microsoft Windows. In its words: “Microsoft Windows DWM Core Library contains a use-after-free vulnerability that allows an authorized attacker to elevate privileges locally.”[1]
The underlying weakness is use after free (CWE-416), in MITRE’s list of common software weaknesses.[2]
It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]
| Product | Fixed in |
|---|---|
| Windows 10 Version 1809 | 10.0.17763.7314 |
| Windows 10 Version 21H2 | 10.0.19044.5854 |
| Windows 10 Version 22H2 | 10.0.19045.5854 |
| Windows 11 version 22H2 | 10.0.22621.5335 |
| Windows 11 version 22H3 | 10.0.22631.5335 |
| Windows 11 Version 23H2 | 10.0.22631.5335 |
| Windows 11 Version 24H2 | 10.0.26100.4061 |
| Windows Server 2019 | 10.0.17763.7314 |
Every device with Microsoft Windows needs the update.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 13 May 2025, within a day of it being made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 3 Jun 2025 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 2%. That’s in the top 21% of the flaws it scores.[4]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
Microsoft has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”[1]
- Update Microsoft Windows now.On Windows: Settings, Windows Update, Check for updates, then restart. Office updates come the same way, or from any Office app: File, Account, Update Options. Then turn on automatic updates, so the next fix arrives on its own.
- Check you’re on 10.0.17763.7314 or later.Fixed in version 10.0.17763.7314, 10.0.19044.5854, 10.0.19045.5854 and 10.0.22621.5335 and others. Anything older is what attackers are going after.
- If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 2%.[4] |
See also
Other Microsoft Windows flaws
- CVE-2026-96951: command injection ·
- CVE-2026-85880: heap-based buffer overflow ·
- CVE-2026-81963: link following ·
- CVE-2008-4250: buffer overflow ·
- CVE-2026-32202: protection mechanism failure ·
- CVE-2025-60710: link following ·
Other use after free flaws
- CVE-2026-109619, PHP: stale internal request-state ·
- CVE-2026-109618, PHP: memory corruption ·
- CVE-2020-9715, Adobe Acrobat: use-after-free ·
- CVE-2026-5281, Google Dawn: use-after-free ·
- CVE-2023-43000, Apple devices: use-after-free ·
Added the same day
- CVE-2025-32709, Microsoft Windows: ancillary function driver for winSock use-after-free ·
- CVE-2025-32706, Microsoft Windows: common log file system (CLFS) driver heap-based buffer overflow ·
- CVE-2025-32701, Microsoft Windows: common log file system (CLFS) driver use-after-free ·
- CVE-2025-30397, Microsoft Windows: scripting engine type confusion ·
Every Microsoft flaw on CISA’s list · Everything added in May 2025
References
- ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Windows DWM Core Library Use-After-Free Vulnerability”. Known Exploited Vulnerabilities Catalog, added 13 May 2025.
- ^ National Institute of Standards and Technology. “CVE-2025-30400 Detail”. National Vulnerability Database, published 13 May 2025.
- ^ Microsoft. Advisories and fixes: msrc.microsoft.com, msrc.microsoft.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.019, percentile 79.9, 31 Oct 2026.
- CVE Program. “CVE-2025-30400”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.