CVE-2017-0199

HIGHNVD 7.89.0▲
EchelonGraph scoreMEDIUM confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Microsoft Office 2007 SP3, Microsoft Office 2010 SP2, Microsoft Office 2013 SP1, Microsoft Office 2016, Microsoft Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, Windows 8.1 allow remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office/WordPad Remote Code Execution Vulnerability w/Windows API."

CVSS v3
7.8
EG Score
9.0(medium)
EPSS
100.0%
KEV
⚠ Exploited

Published

April 12, 2017

Last Modified

April 22, 2026

Advisory Details (8)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft.
generic🟡 PoC Available

Microsoft Excel - OLE Arbitrary Code Execution - Windows dos Exploit

https://www.exploit-db.com/exploits/42995/
generic🔴 Active Exploitation

Microsoft Office Word - '.RTF' Malicious HTA Execution (Metasploit) - Windows remote Exploit

https://www.exploit-db.com/exploits/41934/
generic🟡 PoC Available

Microsoft Word - '.RTF' Remote Code Execution - Windows remote Exploit

https://www.exploit-db.com/exploits/41894/
microsoft Patch Available

Security 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-2017-0199
generic

Analysis of a CVE-2017-0199 Malicious RTF Document – NVISO Labs

https://blog.nviso.be/2017/04/12/analysis-of-a-cve-2017-0199-malicious-rtf-document/
generic
http://www.securitytracker.com/id/1038224
generic
http://www.securityfocus.com/bid/97498
generic

CVE-2017-0199 Practical exploitation ! (PoC)

http://rewtin.blogspot.nl/2017/04/cve-2017-0199-practical-exploitation-poc.html

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 136× in last 7d / 570× 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 747 total refreshes for this CVE.

  1. 2026-07-07 11:23 UTCEG score recompute
  2. 2026-07-07 11:23 UTCVendor advisory
  3. 2026-07-07 11:23 UTCGHSA enrichment
  4. 2026-07-07 07:39 UTCEG score recompute
  5. 2026-07-07 07:39 UTCVendor advisory
  6. 2026-07-07 07:39 UTCGHSA enrichment
  7. 2026-07-07 03:55 UTCEG score recompute
  8. 2026-07-07 03:55 UTCVendor advisory
  9. 2026-07-07 03:55 UTCGHSA enrichment
  10. 2026-07-07 00:12 UTCEG score recompute
  11. 2026-07-07 00:12 UTCVendor advisory
  12. 2026-07-07 00:12 UTCGHSA enrichment
  13. 2026-07-06 20:28 UTCEG score recompute
  14. 2026-07-06 20:28 UTCVendor advisory
  15. 2026-07-06 20:28 UTCGHSA enrichment
  16. 2026-07-06 16:44 UTCEG score recompute
  17. 2026-07-06 16:44 UTCVendor advisory
  18. 2026-07-06 16:44 UTCGHSA enrichment
  19. 2026-07-06 13:01 UTCEG score recompute
  20. 2026-07-06 13:01 UTCVendor advisory
  21. 2026-07-06 13:01 UTCGHSA enrichment
  22. 2026-07-06 09:16 UTCEG score recompute
  23. 2026-07-06 09:16 UTCVendor advisory
  24. 2026-07-06 09:16 UTCGHSA enrichment
  25. 2026-07-06 05:30 UTCEG score recompute
Show 75 more
  1. 2026-07-06 05:30 UTCVendor advisory
  2. 2026-07-06 05:30 UTCGHSA enrichment
  3. 2026-07-06 01:47 UTCEG score recompute
  4. 2026-07-06 01:47 UTCVendor advisory
  5. 2026-07-06 01:47 UTCGHSA enrichment
  6. 2026-07-05 22:04 UTCEG score recompute
  7. 2026-07-05 22:04 UTCVendor advisory
  8. 2026-07-05 22:04 UTCGHSA enrichment
  9. 2026-07-05 18:21 UTCEG score recompute
  10. 2026-07-05 18:21 UTCVendor advisory
  11. 2026-07-05 18:21 UTCGHSA enrichment
  12. 2026-07-05 14:37 UTCEG score recompute
  13. 2026-07-05 14:37 UTCVendor advisory
  14. 2026-07-05 14:37 UTCGHSA enrichment
  15. 2026-07-05 10:53 UTCEG score recompute
  16. 2026-07-05 10:53 UTCVendor advisory
  17. 2026-07-05 10:53 UTCGHSA enrichment
  18. 2026-07-05 07:08 UTCEG score recompute
  19. 2026-07-05 07:08 UTCVendor advisory
  20. 2026-07-05 07:08 UTCGHSA enrichment
  21. 2026-07-05 03:23 UTCEG score recompute
  22. 2026-07-05 03:23 UTCVendor advisory
  23. 2026-07-05 03:23 UTCGHSA enrichment
  24. 2026-07-04 23:38 UTCEG score recompute
  25. 2026-07-04 23:38 UTCVendor advisory
  26. 2026-07-04 23:38 UTCGHSA enrichment
  27. 2026-07-04 19:55 UTCEG score recompute
  28. 2026-07-04 19:55 UTCVendor advisory
  29. 2026-07-04 19:55 UTCGHSA enrichment
  30. 2026-07-04 16:12 UTCEG score recompute
  31. 2026-07-04 16:12 UTCVendor advisory
  32. 2026-07-04 16:12 UTCGHSA enrichment
  33. 2026-07-04 12:29 UTCEG score recompute
  34. 2026-07-04 12:29 UTCVendor advisory
  35. 2026-07-04 12:29 UTCGHSA enrichment
  36. 2026-07-04 08:46 UTCEG score recompute
  37. 2026-07-04 08:46 UTCVendor advisory
  38. 2026-07-04 08:46 UTCGHSA enrichment
  39. 2026-07-04 05:04 UTCEG score recompute
  40. 2026-07-04 05:04 UTCVendor advisory
  41. 2026-07-04 05:03 UTCGHSA enrichment
  42. 2026-07-04 01:20 UTCEG score recompute
  43. 2026-07-04 01:20 UTCVendor advisory
  44. 2026-07-04 01:20 UTCGHSA enrichment
  45. 2026-07-03 21:37 UTCEG score recompute
  46. 2026-07-03 21:37 UTCVendor advisory
  47. 2026-07-03 21:37 UTCGHSA enrichment
  48. 2026-07-03 17:54 UTCEG score recompute
  49. 2026-07-03 17:54 UTCVendor advisory
  50. 2026-07-03 17:54 UTCGHSA enrichment
  51. 2026-07-03 14:09 UTCEG score recompute
  52. 2026-07-03 14:09 UTCVendor advisory
  53. 2026-07-03 14:09 UTCGHSA enrichment
  54. 2026-07-03 10:26 UTCEG score recompute
  55. 2026-07-03 10:26 UTCVendor advisory
  56. 2026-07-03 10:26 UTCGHSA enrichment
  57. 2026-07-03 06:42 UTCEG score recompute
  58. 2026-07-03 06:42 UTCVendor advisory
  59. 2026-07-03 06:42 UTCGHSA enrichment
  60. 2026-07-03 02:58 UTCEG score recompute
  61. 2026-07-03 02:58 UTCVendor advisory
  62. 2026-07-03 02:58 UTCGHSA enrichment
  63. 2026-07-02 23:14 UTCEG score recompute
  64. 2026-07-02 23:14 UTCVendor advisory
  65. 2026-07-02 23:14 UTCGHSA enrichment
  66. 2026-07-02 19:30 UTCEG score recompute
  67. 2026-07-02 19:30 UTCVendor advisory
  68. 2026-07-02 19:30 UTCGHSA enrichment
  69. 2026-07-02 15:48 UTCEG score recompute
  70. 2026-07-02 15:48 UTCVendor advisory
  71. 2026-07-02 15:48 UTCGHSA enrichment
  72. 2026-07-02 12:04 UTCEG score recompute
  73. 2026-07-02 12:04 UTCVendor advisory
  74. 2026-07-02 12:04 UTCGHSA enrichment
  75. 2026-07-02 08:20 UTCEG score recompute

Publicly available exploits

(10 references)

Working exploit code is in the public domain (7 GitHub PoCs) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCjacobsoo/RTF-Cleaner
    First seen Dec 8, 2017

    RTF Cleaner, tries to extract URL from malicious RTF samples using CVE-2017-0199 & CVE-2017-8759

    Open source ↗
  • GitHub PoCnicpenning/RTF-Cleaner
    First seen Nov 3, 2017

    RTF de-obfuscator for CVE-2017-0199 documents to find URLs statically.

    Open source ↗
  • Exploit-DBEDB-42995
    First seen Sep 30, 2017

    Microsoft Excel - OLE Arbitrary Code Execution

    Open source ↗
  • Exploit-DBEDB-41934✓ verified
    First seen Apr 25, 2017

    Microsoft Office Word - '.RTF' Malicious HTA Execution (Metasploit)

    Open source ↗
  • GitHub PoCkn0wm4d/htattack
    First seen Apr 24, 2017

    An exploit implementation for RCE in RTF & DOCs (CVE-2017-0199)

    Open source ↗
  • GitHub PoCn1shant-sinha/CVE-2017-0199
    First seen Apr 23, 2017

    Exploit toolkit CVE-2017-0199 - v2.0 is a handy python script which provides a quick and effective way to exploit Microsoft RTF RCE. It could generate a malicious RTF file and deliver metasploit / meterpreter payload to victim without any complex configuration.

    Open source ↗
  • GitHub PoCExploit-install/CVE-2017-0199
    First seen Apr 22, 2017

    Exploit toolkit CVE-2017-0199 - v2.0 is a handy python script which provides a quick and effective way to exploit Microsoft RTF RCE. It could generate a malicious RTF file and deliver metasploit / meterpreter / any other payload to victim without any complex configuration.

    Open source ↗
  • GitHub PoCmzakyz666/PoC-CVE-2017-0199
    First seen Apr 22, 2017

    Exploit toolkit for vulnerability RCE Microsoft RTF

    Open source ↗
  • GitHub PoChaibara3839/CVE-2017-0199-master
    First seen Apr 19, 2017

    CVE-2017-0199

    Open source ↗
  • Exploit-DBEDB-41894
    First seen Apr 18, 2017

    Microsoft Word - '.RTF' Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2017-0199?
CVE-2017-0199 is a high vulnerability published on April 12, 2017. Microsoft Office 2007 SP3, Microsoft Office 2010 SP2, Microsoft Office 2013 SP1, Microsoft Office 2016, Microsoft Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, Windows 8.1 allow remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office/WordPad Remote Code…
When was CVE-2017-0199 disclosed?
CVE-2017-0199 was first published in the National Vulnerability Database on April 12, 2017, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0199 actively exploited?
Yes. CISA added CVE-2017-0199 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Office and WordPad. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2017-0199?
CVE-2017-0199 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2017-0199?
CVE-2017-0199 affects Microsoft Office and WordPad. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2017-0199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-0199

Explore →

Is Your Infrastructure Affected by CVE-2017-0199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs