CVE-2017-0199

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2017-0566 (ENISA EUVD) · GHSA-mrf9-75pc-cjmm (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 99%CVSS: 7.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

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.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
99%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2017-0199

Published

April 12, 2017

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Nov 16, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: microsoft.
Web page🟡 PoC Available

Microsoft Excel - OLE Arbitrary Code Execution - Windows dos Exploit

https://www.exploit-db.com/exploits/42995/
Web page

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

https://www.exploit-db.com/exploits/41934/
Web page

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

https://www.exploit-db.com/exploits/41894/
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0199
Web page

Philips Intellispace Portal ISP Vulnerabilities | CISA

https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02
Web page

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/
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/97498

Vendor Advisories for CVE-2017-0199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

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

Publicly available exploits

(16 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 3 Exploit-DB entries, 12 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-41934✓ verified
    Published Apr 25, 2017

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

    Open source ↗
  • Metasploitexploit/windows/fileformat/office_word_hta✓ verified
    Published Apr 24, 2017

    Microsoft Office Word Malicious Hta Execution

    Open source ↗
  • GitHub PoCdebugactiveprocess/MaldocTrace
    Published Nov 11, 2026

    Malicious Office document analyzer for defenders, in Go. Emulates VBA and Excel 4.0 macros in a simulated sandbox, rebuilds stomped macros from p-code, detects Equation Editor, CVE-2017-0199 and CVE-2026-21509 exploits, and triages RTF, OneNote, emails and archives into a verdict and IOCs, without running the sample.

    Open source ↗
  • GitHub PoCSunqiz/CVE-2017-0199-reprofuction
    Published Aug 15, 2022

    CVE-2017-0199复现

    Open source ↗
  • GitHub PoCjacobsoo/RTF-Cleaner
    Published 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
    Published Nov 3, 2017

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

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

    Microsoft Excel - OLE Arbitrary Code Execution

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

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

    Open source ↗
  • GitHub PoCn1shant-sinha/CVE-2017-0199
    Published 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
    Published 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 ↗

Frequently asked(6)

What is CVE-2017-0199?
CVE-2017-0199 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2017-0199 was made public on April 11, 2017: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on April 12, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
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 attention. A fix is available. Apply it.
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 (CRITICAL).
Which products are affected by CVE-2017-0199?
CVE-2017-0199 affects Microsoft Office and WordPad.
How do I remediate CVE-2017-0199?
A fix for CVE-2017-0199 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0199 are linked in the Vendor Advisories panel on this page.

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.