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.
CVE-2022-30190
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-06-14), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- —
- EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
June 1, 2022
Last Modified
June 17, 2026
Advisory Details (4)
Auto-updated Jun 3, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-30190Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-30190Packet Storm
http://packetstormsecurity.com/files/167438/Microsoft-Office-Word-MSDTJS-Code-Execution.htmlSecurity Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-30190Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 93× in last 7d / 394× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 697 total refreshes for this CVE.
- 2026-07-22 22:28 UTCEG score recompute
- 2026-07-22 22:28 UTCVendor advisory
- 2026-07-22 22:28 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 18:41 UTCGHSA enrichment
- 2026-07-22 14:54 UTCEG score recompute
- 2026-07-22 14:54 UTCVendor advisory
- 2026-07-22 14:54 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 11:08 UTCVendor advisory
- 2026-07-22 11:07 UTCGHSA enrichment
- 2026-07-22 07:22 UTCVendor advisory
- 2026-07-22 07:22 UTCGHSA enrichment
- 2026-07-22 03:36 UTCVendor advisory
- 2026-07-22 03:36 UTCGHSA enrichment
- 2026-07-21 23:50 UTCVendor advisory
- 2026-07-21 23:50 UTCGHSA enrichment
- 2026-07-21 19:37 UTCVendor advisory
- 2026-07-21 19:37 UTCGHSA enrichment
- 2026-07-21 15:49 UTCVendor advisory
- 2026-07-21 15:49 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:04 UTCVendor advisory
- 2026-07-21 12:04 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 08:18 UTCVendor advisory
- 2026-07-21 08:18 UTCGHSA enrichment
- 2026-07-21 04:32 UTCVendor advisory
- 2026-07-21 04:32 UTCGHSA enrichment
- 2026-07-21 00:46 UTCVendor advisory
- 2026-07-21 00:46 UTCGHSA enrichment
- 2026-07-20 21:00 UTCVendor advisory
- 2026-07-20 21:00 UTCGHSA enrichment
- 2026-07-20 17:15 UTCVendor advisory
- 2026-07-20 17:15 UTCGHSA enrichment
- 2026-07-20 13:30 UTCGHSA enrichment
- 2026-07-20 09:45 UTCVendor advisory
- 2026-07-20 09:45 UTCGHSA enrichment
- 2026-07-20 05:59 UTCVendor advisory
- 2026-07-20 05:59 UTCGHSA enrichment
- 2026-07-20 02:14 UTCVendor advisory
- 2026-07-20 02:14 UTCGHSA enrichment
- 2026-07-19 22:28 UTCVendor advisory
- 2026-07-19 22:28 UTCGHSA enrichment
- 2026-07-19 18:43 UTCVendor advisory
- 2026-07-19 18:43 UTCGHSA enrichment
- 2026-07-19 14:58 UTCVendor advisory
- 2026-07-19 14:58 UTCGHSA enrichment
- 2026-07-19 11:13 UTCVendor advisory
- 2026-07-19 11:13 UTCGHSA enrichment
- 2026-07-19 07:28 UTCVendor advisory
- 2026-07-19 07:28 UTCGHSA enrichment
- 2026-07-19 03:43 UTCVendor advisory
- 2026-07-19 03:43 UTCGHSA enrichment
- 2026-07-18 23:57 UTCGHSA enrichment
- 2026-07-18 20:12 UTCVendor advisory
- 2026-07-18 20:12 UTCGHSA enrichment
- 2026-07-18 16:27 UTCVendor advisory
- 2026-07-18 16:27 UTCGHSA enrichment
- 2026-07-18 12:41 UTCVendor advisory
- 2026-07-18 12:41 UTCGHSA enrichment
- 2026-07-18 08:56 UTCVendor advisory
- 2026-07-18 08:56 UTCGHSA enrichment
- 2026-07-18 05:11 UTCVendor advisory
- 2026-07-18 05:11 UTCGHSA enrichment
- 2026-07-18 01:26 UTCVendor advisory
- 2026-07-18 01:26 UTCGHSA enrichment
- 2026-07-17 21:41 UTCVendor advisory
- 2026-07-17 21:41 UTCGHSA enrichment
- 2026-07-17 17:56 UTCVendor advisory
- 2026-07-17 17:55 UTCGHSA enrichment
- 2026-07-17 14:09 UTCVendor advisory
- 2026-07-17 14:09 UTCGHSA enrichment
- 2026-07-17 10:23 UTCEG score recompute
- 2026-07-17 10:23 UTCVendor advisory
- 2026-07-17 10:23 UTCGHSA enrichment
- 2026-07-17 06:37 UTCVendor advisory
- 2026-07-17 06:37 UTCGHSA enrichment
- 2026-07-17 02:51 UTCVendor advisory
- 2026-07-17 02:51 UTCGHSA enrichment
- 2026-07-16 23:06 UTCVendor advisory
- 2026-07-16 23:06 UTCGHSA enrichment
- 2026-07-16 19:21 UTCVendor advisory
- 2026-07-16 19:21 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 15:34 UTCVendor advisory
- 2026-07-16 15:33 UTCGHSA enrichment
- 2026-07-16 11:48 UTCVendor advisory
- 2026-07-16 11:48 UTCGHSA enrichment
- 2026-07-16 08:02 UTCVendor advisory
- 2026-07-16 08:02 UTCGHSA enrichment
- 2026-07-16 04:17 UTCVendor advisory
- 2026-07-16 04:17 UTCGHSA enrichment
- 2026-07-16 00:32 UTCVendor advisory
- 2026-07-16 00:32 UTCGHSA enrichment
- 2026-07-15 20:47 UTCVendor advisory
- 2026-07-15 20:46 UTCGHSA enrichment
- 2026-07-15 16:59 UTCVendor advisory
- 2026-07-15 16:59 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
Publicly available exploits
(10 references)Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCMalwareTech/FollinaExtractorFirst seen Jun 15, 2022
Extract payload URLs from Follina (CVE-2022-30190) docx and rtf files
Open source ↗ - GitHub PoCHrishikesh7665/Follina_Exploiter_CLIFirst seen Jun 9, 2022
Exploit Microsoft Zero-Day Vulnerability Follina (CVE-2022-30190)
Open source ↗ - GitHub PoCMalwareman007/DeathnoteFirst seen Jun 8, 2022
Proof of Concept of CVE-2022-30190
Open source ↗ - GitHub PoCNoxtal/follinaFirst seen Jun 3, 2022
All about CVE-2022-30190, aka follina, that is a RCE vulnerability that affects Microsoft Support Diagnostic Tools (MSDT) on Office apps such as Word. This is a very simple POC, feel free to check the sources below for more threat intelligence.
Open source ↗ - GitHub PoCkomomon/CVE-2022-30190-follina-Office-MSDT-FixedFirst seen Jun 2, 2022
CVE-2022-30190-follina.py-修改版,可以自定义word模板,方便实战中钓鱼使用。
Open source ↗ - GitHub PoCErrorNoInternet/FollinaScannerFirst seen Jun 2, 2022
A tool written in Go that scans files & directories for the Follina exploit (CVE-2022-30190)
Open source ↗ - GitHub PoCarchanchoudhury/MSDT_CVE-2022-30190First seen May 31, 2022
This Repository Talks about the Follina MSDT from Defender Perspective
Open source ↗ - GitHub PoConecloudemoji/CVE-2022-30190First seen May 31, 2022
CVE-2022-30190 Follina POC
Open source ↗ - GitHub PoCdoocop/CVE-2022-30190First seen May 31, 2022
Microsoft Office Word Rce 复现(CVE-2022-30190)
Open source ↗ - GitHub PoCJMousqueton/PoC-CVE-2022-30190First seen May 30, 2022
POC CVE-2022-30190 : CVE 0-day MS Offic RCE aka msdt follina
Open source ↗
Frequently asked(6)
What is CVE-2022-30190?
When was CVE-2022-30190 disclosed?
Is CVE-2022-30190 actively exploited?
What is the CVSS score of CVE-2022-30190?
Which products are affected by CVE-2022-30190?
How do I remediate CVE-2022-30190?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-30190
Is Your Infrastructure Affected by CVE-2022-30190?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.