CVE-2022-30190 Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability
A remote code execution vulnerability exists when MSDT is called using the URL protocol from a calling application such as Word. An attacker who successfully exploits this vulnerability can run code with the privileges of the calling application.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 14 Jun 2022.
- CISA lists it as known to be used in ransomware campaigns.
- Rated High severity (CVSS 7.8, scored by Vendor).
- It has been in the catalogue for 1,606 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
A remote code execution vulnerability exists when MSDT is called using the URL protocol from a calling application such as Word. An attacker who successfully exploits this vulnerability can run arbitrary code with the privileges of the calling application. The attacker can then install programs, view, change, or delete data, or create new accounts in the context allowed by the user’s rights. Please see the MSRC Blog Entry for important information about steps you can take to protect your system from this vulnerability.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Windows 10 Version 1809 | 10.0.17763.0 to before 10.0.17763.3046 |
| Microsoft Windows 10 Version 1809 | 10.0.0 to before 10.0.17763.3046 |
| Microsoft Windows Server 2019 | 10.0.17763.0 to before 10.0.17763.3046 |
| Microsoft Windows Server 2019 (Server Core installation) | 10.0.17763.0 to before 10.0.17763.3046 |
| Microsoft Windows 10 Version 21H1 | 10.0.0 to before 10.0.19043.1766 |
| Microsoft Windows Server 2022 | 10.0.20348.0 to before 10.0.20348.770 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
- 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
Vendor Advisories
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2022-30190 and every other exploited flaw on the list.