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 9 Dec 2022.
Windows 10 1507Operating system · Microsoft

CVE-2022-41128

HIGH · 8.8 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 10.0.10240.19567 / 10.0.14393.5501 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
Windows Scripting Languages Remote Code Execution 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 · moderate confidence

This is a Remote Code Execution vulnerability in Windows Scripting Languages (which includes VBScript, JScript, and related scripting engines). The vulnerability allows an attacker to execute arbitrary code on affected Windows systems, likely through malicious script files or web-based attacks targeting the scripting engine.

MitigationApply the Microsoft security updates for CVE-2022-41128 immediately. Until patches are applied, restrict execution of VBScript/JScript files and disable Active Scripting in Internet Explorer as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.19567
Windows 10 1607Operating system
Affected:< 10.0.14393.5501
Windows 10 1809Operating system
Affected:< 10.0.17763.3650
Windows 10 20h2Operating system
Affected:< 10.0.19042.2251
Windows 10 21h1Operating system
Affected:< 10.0.19043.2251
Windows 10 21h2Operating system
Affected:< 10.0.19044.2251
Windows 10 22h2Operating system
Affected:< 10.0.19045.2251
Windows 11 21h2Operating system
Affected:< 10.0.22000.1219

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Windows version and build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the exact Windows build. Alternatively, run 'ver' at command prompt.
    Affected if The displayed build number is lower than any of the following thresholds: 10.0.10240.19567 (Win10 1507), 10.0.14393.5501 (Win10 1607), 10.0.17763.3650 (Win10 1809), 10.0.19042.2251 (Win10 20h2), 10.0.19043.2251 (Win10 21h1), 10.0.19044.2251 (Win10 21h2), 10.0.19045.2251 (Win10 22h2), or 10.0.22000.1
  2. Check if VBScript or JScript is enabled in Internet Explorer
    Open Internet Explorer, go to Internet Options > Security > Custom Level. Look for 'Script ActiveX controls marked safe for scripting' and 'Script ActiveX controls not marked as safe'. Also check 'Enable VBScript' and 'Enable JScript' settings in the same area.
    Affected if Any of these scripting options are set to 'Enable' or 'Prompt' rather than 'Disable'. The vulnerability can be triggered when VBScript/JScript executes in IE or IE Mode in Edge.
  3. Check if Internet Explorer mode is enabled in Microsoft Edge
    Open Microsoft Edge, go to Settings > Default browser. Look for the 'Internet Explorer mode' setting under 'Compatibility'. Alternatively, check Group Policy settings at Computer Configuration > Administrative Templates > Windows Components > Microsoft Edge > Configure Internet Explorer mode integration.
    Affected if Internet Explorer mode is enabled, as this allows legacy VBScript/JScript engine execution within Edge.
  4. Verify vulnerable VBScript/JScript engine DLLs are present
    Check for vbscript.dll and jscript.dll in the System32 folder (typically C:\Windows\System32\). Right-click each file, select Properties, and view the Version tab to see file version.
    Affected if These DLLs exist on the system (they are present by default in Windows) AND the Windows version is below the patched builds listed above.

You are affected if your Windows build is below any of the specified thresholds AND VBScript/JScript is enabled or accessible (including via IE Mode in Edge), allowing specially crafted content to trigger the scripting engine vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.19567 / 10.0.14393.5501 / 10.0.17763.3650 or later
Fixed in 10.0.10240.1956710.0.14393.550110.0.17763.3650
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security updates for CVE-2022-41128 immediately. Until patches are applied, restrict execution of VBScript/JScript files and disable Active Scripting in Internet Explorer as a defense-in-depth measure.

Recommended fix High confidence

Windows 10 build 10.0.10240.19567 (1507) / 10.0.14393.5501 (1607) / 10.0.17763.3650 (1809) / 10.0.19042.2251 (20h2) / 10.0.19043.2251 (21h1) / 10.0.19044.2251 (21h2) / 10.0.19045.2251 (22h2); Windows 11 21h2 build 10.0.22000.1219

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 release (1507, 1607, 1809, 20h2, 21h1, 21h2, or 22h2) or Windows 11 21h2 is installed
  3. For Windows 10 1507: Install KB5020035 or later to reach build 10.0.10240.19567
  4. For Windows 10 1607: Install KB5020030 or later to reach build 10.0.14393.5501
  5. For Windows 10 1809: Install KB5020036 or later to reach build 10.0.17763.3650
  6. For Windows 10 20h2: Install KB5020037 or later to reach build 10.0.19042.2251
  7. For Windows 10 21h1: Install KB5020038 or later to reach build 10.0.19043.2251
  8. For Windows 10 21h2: Install KB5020044 or later to reach build 10.0.19044.2251
Caveat None - these are cumulative security updates that include only vulnerability fixes with no functional changes

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41128 — 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-2022-41128 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