CVE-2017-0262 — OFFICE
HIGHCVE-2017-0262 is a high-severity (CVSS 7.8) remote code execution vulnerability in microsoft office. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-02-10) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-02-10. Federal agencies were required to remediate by 2022-08-10.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-0262.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2017-0262 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0261 and CVE-2017-0281.
Affected Products
officemicrosoftResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remo…
Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remo…
Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remo…
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every microsoft office deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2017-0262 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2017-0262 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.