dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Sep 2024.
Windows 10 1507Operating system · Microsoft

CVE-2024-38178

HIGH · 7.5 CVSS v3.1 Developing Published 2024-08-13
Fix available
A fix is available. Upgrade to 10.0.10240.20751 / 10.0.14393.7259 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Scripting Engine Memory Corruption Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-23.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20751
Windows 10 1607Operating system
Affected:< 10.0.14393.7259
Windows 10 1809Operating system
Affected:< 10.0.17763.6189
Windows 10 21h2Operating system
Affected:< 10.0.19044.4780
Windows 10 22h2Operating system
Affected:< 10.0.19045.4780
Windows 11 21h2Operating system
Affected:< 10.0.22000.3147
Windows 11 22h2Operating system
Affected:< 10.0.22621.4037
Windows 11 23h2Operating system
Affected:< 10.0.22631.4037

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20751 / 10.0.14393.7259 / 10.0.17763.6189 or later
Fixed in 10.0.10240.2075110.0.14393.725910.0.17763.6189
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Apply the corresponding security update: Windows 10 1507 to build 10.0.10240.20751 or later | Windows 10 1607 to build 10.0.14393.7259 or later | Windows 10 1809 to build 10.0.17763.6189 or later | Windows 10 21h2 to build 10.0.19044.4780 or later | Windows 10 22h2 to build 10.0.19045.4780 or later

  1. Open Settings on the Windows system and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates from Microsoft Update
  3. Alternatively, manually download the specific security update for your Windows version from the Microsoft Update Catalog (search for CVE-2024-38178)
  4. After installation, restart the system to apply the update
  5. Verify the update was installed by checking Windows Update history - the specific KB number for this CVE can be found in the Microsoft Security Response Center advisory
Caveat Standard Windows security update with no expected breaking changes; as with any system update, test critical applications before deploying broadly in enterprise environments

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get it fixed fast

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38178 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data