How severe is CVE-2017-0199?

CVE-2017-0199 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2017-0199?

Affected package information for CVE-2017-0199 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2017-0199?

No patch has shipped for CVE-2017-0199 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2017-0199 across my infrastructure?

Inventory every microsoft office deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2017-0199 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2017-0199?

O3 detects and blocks CVE-2017-0199 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2017-0199 actively exploited in the wild?

Yes. There are 31 known exploit references for CVE-2017-0199, including 3 documented proof-of-concept exploits on Exploit-DB and 21 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-0199?

CVE-2017-0199 has an EPSS (Exploit Prediction Scoring System) score of 99.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-0199 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-0199 (Microsoft Office and WordPad Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2017-0199?

CVE-2017-0199 affects microsoft office (4 versions, e.g. 2007, 2010, 2013…); microsoft windows 7; microsoft windows server 2008 (1 version, e.g. r2); microsoft windows server 2012, and 2 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2017-0199?

A Metasploit module references CVE-2017-0199, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-0199 published, and has it been updated?

CVE-2017-0199 was published on April 12, 2017 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03 · Ransomware

CVE-2017-0199

HIGH

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…

Published

Apr 12, 2017

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

31 known

EPSS Exploitation Probability

via FIRST.org ↗

99.9%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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."

Affected Products

6 products · 11 configurations

Application

officemicrosoft

4 versions

2007201020132016

windows 7microsoft

all

windows server 2008microsoft

1 version

windows server 2012microsoft

all

windows vistamicrosoft

all

Application

intellispace portalphilips

2 versions

7.08.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-42995doswindows

Microsoft Excel - OLE Arbitrary Code Execution

by Eduardo Braun Prado · Sep 30, 2017

Exploit-DB Source

EDB-41934remotewindows✓ Verified

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

by Metasploit · Apr 25, 2017

Exploit-DB Source

EDB-41894remotewindows

Microsoft Word - '.RTF' Remote Code Execution

by Bhadresh Patel · Apr 18, 2017

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft office deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2017-0199 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2017-0199 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2017-0199. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2017-0199 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2017-0199 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2017-0199

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2017-0199 being exploited in your environment?