CVE-2017-0261
HIGHCISA KEVEPSS 100th pctlDescription
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.
How to fix
Actively exploited, no published fix found yet
CISA required action: Apply updates per vendor instructions.
Federal remediation due: 2022-03-24
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 100% of all known CVEs.
Microsoft Office Use-After-Free Vulnerability
Microsoft Office contains a use-after-free vulnerability which can allow for remote code execution.
Apply updates per vendor instructions.
Remediation due: 2022-03-24
References
Related Vulnerabilities
Other CWE-416 (Use After Free) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-0708 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-31166 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-5119 | Critical | 9.8 | 99% | KEV | - |
| CVE-2010-3962 | High | 8.1 | 96% | KEV | - |
| CVE-2015-0313 | Critical | 9.8 | 96% | KEV | Fix |
| CVE-2021-34833 | High | 7.8 | 96% | - | - |
Common questions
How do I fix CVE-2017-0261?
No published fix for CVE-2017-0261 has been found yet. It is on the CISA Known Exploited Vulnerabilities list; federal agencies must remediate by 2022-03-24. Apply the vendor's mitigations per CISA's guidance.
Is CVE-2017-0261 being actively exploited?
Yes. CVE-2017-0261 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2022-03-24. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2017-0261?
CVE-2017-0261 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2017-0261
Markdown
[](https://tridentstack.com/cve/CVE-2017-0261)HTML
<a href="https://tridentstack.com/cve/CVE-2017-0261"><img src="https://tridentstack.com/cve/badge/CVE-2017-0261.svg" alt="CVE-2017-0261"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-04-22.