CVE-2024-38178
CVE-2024-38178 is a security flaw in Microsoft Windows, Microsoft’s operating system for PCs and servers. Attackers can run their own code on Microsoft Windows from anywhere, without logging in. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 13 Aug 2024.[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.26100.1457, 10.0.17763.6189, 10.0.20348.2655 and 10.0.22000.3147 and others.
Description
CISA calls it a scripting engine memory corruption in Microsoft Windows. In its words: “Microsoft Windows Scripting Engine contains a memory corruption vulnerability that allows unauthenticated attacker to initiate remote code execution via a specially crafted URL.”[1]
The underlying weakness is type confusion (CWE-843), in MITRE’s list of common software weaknesses.[2]
It scores 7.5 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 11 Version 24H2 | 10.0.26100.1457 |
| Windows 10 Version 1809 | 10.0.17763.6189 |
| Windows Server 2019 | 10.0.17763.6189 |
| Windows Server 2019 (Server Core installation) | 10.0.17763.6189 |
| Windows Server 2022 | 10.0.20348.2655 |
| Windows 11 version 21H2 | 10.0.22000.3147 |
| Windows 10 Version 21H2 | 10.0.19044.4780 |
| Windows 11 version 22H2 | 10.0.22621.4037 |
Every device with Microsoft Windows needs the update.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 13 Aug 2024, 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 Sep 2024 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 41%. That’s in the top 2% 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 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.26100.1457 or later.Fixed in version 10.0.26100.1457, 10.0.17763.6189, 10.0.20348.2655 and 10.0.22000.3147 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.5.[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 41%.[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 type confusion flaws
- CVE-2026-85046, Chrome and other Chromium browsers: type confusion ·
- CVE-2025-13223, Chrome and other Chromium browsers: type confusion ·
- CVE-2025-10585, Chrome and other Chromium browsers: type confusion ·
- CVE-2025-6554, Chrome and other Chromium browsers: type confusion ·
- CVE-2024-7971, Chrome and other Chromium browsers: type confusion ·
Added the same day
- CVE-2024-38213, Microsoft Windows: smartScreen security feature bypass ·
- CVE-2024-38193, Microsoft Windows: ancillary function driver for winSock privilege escalation ·
- CVE-2024-38189, Microsoft Project: remote code execution ·
- CVE-2024-38107, Microsoft Windows: power dependency coordinator privilege escalation ·
- CVE-2024-38106, Microsoft Windows: kernel privilege escalation ·
Every Microsoft flaw on CISA’s list · Everything added in August 2024
References
- ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Windows Scripting Engine Memory Corruption Vulnerability”. Known Exploited Vulnerabilities Catalog, added 13 Aug 2024.
- ^ National Institute of Standards and Technology. “CVE-2024-38178 Detail”. National Vulnerability Database, published 13 Aug 2024.
- ^ Microsoft. Advisories and fixes: msrc.microsoft.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.414, percentile 98.7, 31 Oct 2026.
- CVE Program. “CVE-2024-38178”. 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.