CVE-2017-0261
Microsoft Office Use-After-Free
- Published12 May 2017
- Added to CISA KEV3 Mar 2022
- Remediation due24 Mar 2022
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-0262 and CVE-2017-0281.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2017-0261 being actively exploited?
Yes. CVE-2017-0261 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Mar 2022.
How severe is CVE-2017-0261?
CVE-2017-0261 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 78.1% probability of exploitation.
Which products are affected by CVE-2017-0261?
Affected products include Microsoft Office.
How do I fix CVE-2017-0261?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2017-0261 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Running Microsoft 365?
Patching is one half. Scan your domain and check MFA, legacy authentication, admin roles and mail forwarding in two minutes, with a fix for every gap.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.