What it is
CVE-2024-38178 is an unauthenticated Scripting Engine Memory Corruption Vulnerability affecting Microsoft Windows 11 Version 24H2 and 18 other products.
Vulnerability report
Scripting Engine Memory Corruption Vulnerability
Microsoft / Windows 11 Version 24H2 · affected before 10.0.26100.1457
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2024-38178 is an unauthenticated Scripting Engine Memory Corruption Vulnerability affecting Microsoft Windows 11 Version 24H2 and 18 other products.
Have exploitation attempts been observed?
Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Confidence is confirmed.
Who is affected?
Affected products include Microsoft / Windows 11 Version 24H2 and 18 other products, including affected before 10.0.26100.1457, affected before 10.0.17763.6189, and affected before 10.0.20348.2655.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
Scripting Engine Memory Corruption Vulnerability
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CISA
A trusted third party reported exploitation attempts.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CISA First | 2024-08-13 00:00 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Nessus template detected 02 Jun 2025.
View Nessus template (opens in new tab)No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Scanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nessus | https://www.tenable.com/plugins/nessus/205461 | 02 Jun 2025 |
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
EPSS
41.4%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · Google Threat Intelligence
Written by: Casey Charrier, James Sadowski, Clement Lecigne, Vlad Stolyarov Executive Summary Google Threat Intelligence Group (GTIG) tracked 75 zero-day vulnerabilities exploited in the wild in 2024, a decrease from the number we identified in 2023 (98 vulnerabilities), but...
Read full advisoryRecent mention · Google Threat Intelligence
Written by: Casey Charrier, James Sadowski, Clement Lecigne, Vlad Stolyarov Executive Summary Google Threat Intelligence Group (GTIG) tracked 75...Google Threat Intelligence · 29 Apr 2025
Written by: Casey Charrier, James Sadowski, Clement Lecigne, Vlad Stolyarov Executive Summary Google Threat Intelligence Group (GTIG) tracked 75 zero-day vulnerabilities exploited in the wild in 2024, a decrease from the number we identified in 2023 (98 vulnerabilities), but still an increase from 2022 (63 vulnerabilities). We divided the reviewed vulnerabilities into two main categories: end-user platforms and products (e.g., mobile devices, operating systems, and browsers) and enterprise-focused technologies, such as security software and appliances. Vendors continue to drive...
Timeline
09:26 UTC
Scanner coverage available
17:29 UTC
Vulnerability disclosed publicly
00:00 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
22:36 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2024-38178
Sample API response{
"cve_id": "CVE-2024-38178",
"confidence": "Confirmed",
"cvss_score": 7.5,
"cvss_estimated": false,
"epss_score": 0.4138,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}