Vulnerability report

Trusted Third Party Report Confirmed Confidence In CISA KEV

CVE-2022-30190

Windows 10 Version 1809 Remote Code Execution

Microsoft / Windows 10 Version 1809 · affected before 10.0.17763.3046

Severity
CVSS 7.8 · High
Confidence
Confirmed
Exploit status
Trusted Third Party Report
EPSS
98.5%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

A remote code execution vulnerability exists when MSDT is called using the URL protocol from a calling application such as Word.

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. Also reported by third-party sources. Confidence is confirmed.

Who is affected?

Affected products include Microsoft / Windows 10 Version 1809 and 21 other products, including affected before 10.0.17763.3046, affected before 10.0.17763.3046, and affected before 10.0.19043.1766.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Windows 10 Version 1809 Remote Code Execution

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.

Microsoft Affected
Windows 10 Version 1809
Before 10.0.17763.3046
Microsoft Affected
Windows Server 2019
Before 10.0.17763.3046
Microsoft Affected
Windows Server 2019 (Server Core installation)
Before 10.0.17763.3046
Microsoft Affected
Windows 10 Version 21H1
Before 10.0.19043.1766
Microsoft Affected
Windows Server 2022
Before 10.0.20348.770
Microsoft Affected
Windows 10 Version 20H2
Before 10.0.19042.1766
Microsoft Affected
Windows Server version 20H2
Before 10.0.19042.1766
Microsoft Affected
Windows 11 version 21H2
Before 10.0.22000.739
Microsoft Affected
Windows 10 Version 21H2
Before 10.0.19044.1766
Microsoft Affected
Windows 10 Version 1507
Before 10.0.10240.19325
Microsoft Affected
Windows 10 Version 1607
Before 10.0.14393.5192
Microsoft Affected
Windows Server 2016
Before 10.0.14393.5192
Microsoft Affected
Windows Server 2016 (Server Core installation)
Before 10.0.14393.5192
Microsoft Affected
Windows 7
Before 6.1.7601.25984
Microsoft Affected
Windows 7 Service Pack 1
Before 6.1.7601.25984
Microsoft Affected
Windows 8.1
Before 6.3.9600.20402
Microsoft Affected
Windows Server 2008 R2 Service Pack 1
Before 6.1.7601.25984
Microsoft Affected
Windows Server 2008 R2 Service Pack 1 (Server Core installation)
Before 6.1.7601.25984
Microsoft Affected
Windows Server 2012
Before 6.2.9200.23736
Microsoft Affected
Windows Server 2012 (Server Core installation)
Before 6.2.9200.23736
Microsoft Affected
Windows Server 2012 R2
Before 6.3.9600.20402
Microsoft Affected
Windows Server 2012 R2 (Server Core installation)
Before 6.3.9600.20402
View vendor advisory (opens in new tab)
Published
01 Jun 2022
Exploitation Attempts Reported
14 Jun 2022
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required

Tags

metasploit cisa microsoft windows malware metasploit_scanner

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

CISA

Recorded 14 Jun 2022

A trusted third party reported exploitation attempts.

Targeted by Malware-Related Exploitation Attempts

CISA

Recorded 02 Jun 2026

Exploitation attempts against this vulnerability are associated with malware-related payloads.

Proof of concept available

GitHub

Recorded 30 May 2022

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2022-06-14 00:00 UTC
Tenable Blog 2026-06-02 14:21 UTC
CVE 2026-08-04 04:41 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.8 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

98.5%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Recent mention · Tenable Blog

Inside the customer environment: Where threat actors, vulnerabilities, and exposed assets intersect

Tenable Research has developed a graph-based model linking 600+ threat groups to real-world customer exposures. It reveals which vulnerabilities sit at the intersection of severity, active exploitation, and organizational risk.Key takeawaysThe "patch everything" strategy is...

Read full advisory

All CVSS Scores

CVSS v3.1 7.8 High

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

CVSS v2.0 9.3 High

AV:N/AC:M/Au:N/C:C/I:C/A:C

All Mentions

Recent mention · Tenable Blog

Inside the customer environment: Where threat actors, vulnerabilities, and exposed assets intersect

Tenable Blog · 27 May 2026

Tenable Research has developed a graph-based model linking 600+ threat groups to real-world customer exposures. It reveals which vulnerabilities sit at the intersection of severity, active exploitation, and organizational risk.Key takeawaysThe "patch everything" strategy is dead: Vulnerability prioritization based on exploitation risk offers a path forward. A directed graph model linking 600+ threat actors to vulnerabilities in 7,800 customer environments reveals that 68% of organizations carry at least one CVE previously exploited by a named adversary, and 321 tracked threat groups can...

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

word_msdtjs_rce

metasploit · Created Unknown

Metasploit module for CVE-2022-30190

Timeline

From disclosure to observed exploitation attempts

  1. 04:41 UTC

    KEV confirmed by CVE

    Exploitation attempts reported by an external source

  2. 14:21 UTC

    KEV confirmed by Tenable Blog

    Exploitation attempts reported by an external source

  3. 14:08 UTC

    Targeted by malware-related exploitation attempts

    Malware-related exploitation attempts or payloads reported

  4. 15:02 UTC

    Metasploit module available

    Exploit module available

  5. 15:02 UTC

    Public PoC available

    Public proof-of-concept code published

  6. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  7. 20:10 UTC

    CVE published

    Vulnerability disclosed publicly

  8. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2022-30190

Sample API response
{
  "cve_id": "CVE-2022-30190",
  "confidence": "Confirmed",
  "cvss_score": 7.8,
  "cvss_estimated": false,
  "epss_score": 0.98494,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}