Skip to content
Server Security Center
KEVhigh7.5

CVE-2025-30397: Microsoft Windows Scripting Engine Type Confusion

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-05-13.

CVSS v3.1 (CVE record)
7.5
high
EPSS (exploit probability, 30 days)
27%
higher than 98.1% of all CVEs
Added to CISA KEV
2025-05-13
US federal due date 2025-06-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-30397 explained

CVE-2025-30397 is a type confusion flaw (CWE-843) in the Microsoft Scripting Engine on Windows. It allows an unauthorized attacker to execute code over a network. CISA lists it as known to be exploited, so affected Windows client and server systems need prompt patching.

Impact

A successful attacker can execute code on the target system without prior privileges. Confidentiality, integrity and availability impacts are all high. Exploitation is network-based but needs user interaction and has high attack complexity. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so attacks are less likely to run at scale without manual steps. Attackers are known to use this vulnerability.

Who is affected

Affected are Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2, Windows 11 versions 22H2, 22H3, 23H2 and 24H2, and Windows Server 2008 R2 SP1 (including Server Core) and Server 2008 SP2. Example fixed builds: 10.0.19045.5854 (Windows 10 22H2), 10.0.26100.4061 (Windows 11 24H2), 10.0.22631.5335 (Windows 11 23H2), 6.1.7601.27729 (Server 2008 R2 SP1), 6.0.6003.23279 (Server 2008 SP2). Earlier builds are affected. The page lists 13 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

Access of resource using incompatible type ('type confusion') in Microsoft Scripting Engine allows an unauthorized attacker to execute code over a network.

CISA 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.21014
    Fixed in
    • 10.0.10240.21014
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.8066
    Fixed in
    • 10.0.14393.8066
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7314
    Fixed in
    • 10.0.17763.7314
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5854
    Fixed in
    • 10.0.19044.5854
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5854
    Fixed in
    • 10.0.19045.5854
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5335
    Fixed in
    • 10.0.22621.5335
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5335
    Fixed in
    • 10.0.22631.5335
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5335
    Fixed in
    • 10.0.22631.5335
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.4061
    Fixed in
    • 10.0.26100.4061
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27729
    Fixed in
    • 6.1.7601.27729
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27729
    Fixed in
    • 6.1.7601.27729
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23279
    Fixed in
    • 6.0.6003.23279
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23279
    Fixed in
    • 6.0.6003.23279
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25475
    Fixed in
    • 6.2.9200.25475
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25475
    Fixed in
    • 6.2.9200.25475
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22577
    Fixed in
    • 6.3.9600.22577
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22577
    Fixed in
    • 6.3.9600.22577
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8066
    Fixed in
    • 10.0.14393.8066
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8066
    Fixed in
    • 10.0.14393.8066
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7314
    Fixed in
    • 10.0.17763.7314
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7314
    Fixed in
    • 10.0.17763.7314
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3692
    Fixed in
    • 10.0.20348.3692
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1611
    Fixed in
    • 10.0.25398.1611
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.4061
    Fixed in
    • 10.0.26100.4061
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.4061
    Fixed in
    • 10.0.26100.4061

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.21014
    • Microsoft Windows 10 Version 1607: 10.0.14393.8066
    • Microsoft Windows 10 Version 1809: 10.0.17763.7314
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5854
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5854
    • Microsoft Windows 11 version 22H2: 10.0.22621.5335
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-30397
  • CISA's deadline for US federal agencies: 2025-06-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that raises each system to the fixed build listed for its Windows version.
  2. Prioritize systems where users browse the web or open untrusted content, since exploitation requires user interaction.
  3. Follow the Microsoft advisory for mitigations on any system that cannot be patched immediately.
  4. Per CISA, discontinue use of the product if mitigations are unavailable; US federal agencies must act by 2025-06-03.
  5. Check unpatched systems for signs of compromise, given that the vulnerability is known to be exploited.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2025-30397

Is CVE-2025-30397 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-13. Whether it is used in ransomware campaigns is unknown.
Does an attacker need an account on the system?
No privileges are required. However, exploitation requires user interaction and has high attack complexity.
Are Windows Server 2008 systems covered?
Yes. The CVE record lists fixed builds 6.1.7601.27729 for Windows Server 2008 R2 SP1 (including Server Core) and 6.0.6003.23279 for Windows Server 2008 SP2.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.