What is CVE-2017-0199?
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."
The record classifies CVE-2017-0199 under weakness class NVD-CWE-noinfo. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 11 affected-product entries are recorded, across 2 vendors, listed below. The identifier was first published 3486 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.8 — HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 99.4% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
- CISA KEV
- Listed since 2021-11-03, federal remediation deadline 2022-05-03 — used in known ransomware campaigns
- Threadlinqs priority
- 10/10 — CISA lists it as used in ransomware, which Threadlinqs scores at the maximum
- Published
- 2017-04-12, last modified 2025-10-21
Is CVE-2017-0199 being exploited?
CISA added CVE-2017-0199 to the Known Exploited Vulnerabilities catalog on 2021-11-03, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2022-05-03 under BOD 22-01. CISA flags the vulnerability as one used in known ransomware campaigns. Weaponised exploit code for CVE-2017-0199 is publicly available. 11 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 58 in the Threadlinqs vulnerability feed.
- bhdresh/CVE-2017-0199 (github)
- haibara3839/CVE-2017-0199-master (github)
- NotAwful/CVE-2017-0199-Fix (github)
- SyFi/cve-2017-0199 (github)
- Exploit-install/CVE-2017-0199 (github)
- jacobsoo/RTF-Cleaner (github)
- mzakyz666/PoC-CVE-2017-0199 (github)
- n1shant-sinha/CVE-2017-0199 (github)
Affected products and versions
- Microsoft: Office 2007, Office 2010, Office 2013, Office 2016, Windows 7, Windows Server 2008, Windows Server 2008 r2, Windows Server 2012, Windows Vista
- Philips: Intellispace Portal 7.0, Intellispace Portal 8.0
How to fix CVE-2017-0199
The record marks a vendor fix as available for CVE-2017-0199. Patch reference: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-0199. Vendor advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0199. Because CVE-2017-0199 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2022-05-03. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2017-0199
6 tracked threats in the Threadlinqs corpus reference CVE-2017-0199, either in the campaign’s CVE list or as an indicator on the campaign record.
- Q2 2026 Vulnerability and Exploit Landscape: Exploited AI-platform flaws (OpenClaw CVE-2026-25253, Dify CVE-2026-41948, Open WebUI CVE-2026-45386), Exchange CVE-2026-45501, and Linux kernel page-cache LPE exploit wave (Copy Fail, Dirty Frag) — HIGH · 2026-10-20
- Remcos RAT phishing campaign disguised as project material purchase requests exploits CVE-2017-0199 against Korean companies — HIGH · 2026-09-28
- Remcos RAT Delivered via CVE-2017-0199 Phishing Campaign Impersonating Payment Confirmations — HIGH · 2026-07-13
- MuddyWater Operation Olalampo — Iran MOIS-Nexus APT Deploys New Malware Variants with Telegram Bot C2 Targeting Middle Eastern Governments and Critical Infrastructure — HIGH · 2026-02-28
- APT28 Microsoft Office Security Feature Bypass (CVE-2026-21509) — CISA KEV, Targeting Ukraine & EU via COREPER-Themed Spear-Phishing — HIGH · 2026-02-23
- CVE-2026-21509: Russian Hackers Exploit Microsoft Office Vulnerability Against Ukraine — CRITICAL · 2026-02-03
Sources
Enriched from CVE.org, FIRST EPSS, CISA KEV, public proof-of-concept repositories. Last verified by Threadlinqs on .