CVE-2022-41128: Microsoft Windows Scripting Languages Remote Code Execution
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-11-08.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 25%
- higher than 97.9% of all CVEs
- Added to CISA KEV
- 2022-11-08
- US federal due date 2022-12-09
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2022-41128 explained
CVE-2022-41128 is a remote code execution vulnerability in the JScript9 scripting language in Microsoft Windows, classified as an out-of-bounds write. CISA lists it as known to be exploited by attackers, and it affects a wide range of Windows 7, 8.1, 10 and 11 releases, making prompt patching important.
Impact
A remote attacker needs no privileges, but a user must take an action, such as interacting with attacker-controlled content. Successful exploitation allows code execution with high impact on confidentiality, integrity and availability. CISA rates the issue as automatable, meaning it can be exploited at scale, with total technical impact, meaning full control of the affected component. Attackers are known to exploit it. Ransomware use is unknown.
Who is affected
The CVE record lists Windows 10 versions 1507, 1607, 1809, 20H2, 21H1, 21H2 and 22H2. It also lists Windows 11 versions 21H2 and 22H2, Windows 7, Windows 7 Service Pack 1 and Windows 8.1. Fixed builds include 10.0.10240.19567, 10.0.14393.5501, 10.0.17763.3650, 10.0.19042.2251, 10.0.19043.2251, 10.0.19044.2251, 10.0.19045.2251, 10.0.22000.1219, 10.0.22621.819, 6.1.7601.26221 (Windows 7) and 6.3.9600.20671 (Windows 8.1). Further products are listed on this page.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows contains an unspecified vulnerability in the JScript9 scripting language which allows for remote code execution.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.19567
- 10.0.10240.19567
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.2251
- 10.0.19042.2251
- Microsoft Windows 10 Version 21H132-bit, ARM64, x64AffectedFixed in
- < 10.0.19043.2251
- 10.0.19043.2251
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.2251
- 10.0.19044.2251
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.2251
- 10.0.19045.2251
- Microsoft Windows 11 version 21H2ARM64, x64AffectedFixed in
- < 10.0.22000.1219
- 10.0.22000.1219
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.819
- 10.0.22621.819
- Microsoft Windows 732-bitAffectedFixed in
- < 6.1.7601.26221
- 6.1.7601.26221
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 10 Version 21H132-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 21H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 732-bit |
|
|
Show 8 more products
- Microsoft Windows 7 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26221
- 6.1.7601.26221
- Microsoft Windows 8.132-bit, ARM64, x64AffectedFixed in
- < 6.3.9600.20671
- 6.3.9600.20671
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26221
- 6.1.7601.26221
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23968
- 6.2.9200.23968
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20671
- 6.3.9600.20671
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1249
- 10.0.20348.1249
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 7 Service Pack 1x64 |
|
|
| Microsoft Windows 8.132-bit, ARM64, x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.19567
- Microsoft Windows 10 Version 1607: 10.0.14393.5501
- Microsoft Windows 10 Version 1809: 10.0.17763.3650
- Microsoft Windows 10 Version 20H2: 10.0.19042.2251
- Microsoft Windows 10 Version 21H1: 10.0.19043.2251
- Microsoft Windows 10 Version 21H2: 10.0.19044.2251
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41128
- CISA's deadline for US federal agencies: 2022-12-09 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to at least the fixed build listed for its Windows version.
- Follow the vendor advisory, as CISA's required action states: apply updates per vendor instructions.
- Prioritize internet-facing systems and systems whose users browse the web or open external content.
- Verify the installed build numbers across your fleet to confirm the update is applied.
- Check systems that remained unpatched for signs of compromise, since attackers are known to exploit this vulnerability.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-787 Out-of-bounds Write
Questions about CVE-2022-41128
- Is CVE-2022-41128 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-11-08, with a US federal due date of 2022-12-09. Whether it is used in ransomware campaigns is unknown.
- Does exploitation require user action?
- Yes. The CVSS vector shows that user interaction is required, but the attacker needs no privileges and can attack over the network with low complexity.
- Which Windows build fixes the issue on Windows 11 22H2?
- The CVE record lists
10.0.22621.819as the fixed build for Microsoft Windows 11 version 22H2. Earlier builds are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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-22. Always confirm with the vendor's or distribution's advisory before patching.