CVE-2017-11882: Remote Code Execution in Microsoft Office Equation Editor
- Vendor
- Microsoft Corporation
CVE-2017-11882 is a stack-based buffer overflow in the legacy Microsoft Equation Editor component of Microsoft Office. Improper bounds checking during equation font-name processing allows a crafted embedded equation object to corrupt stack memory and execute arbitrary code with the privileges of the user opening the document. Affected products include Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, and Office 2016, including affected 32-bit and 64-bit editions. Exploits commonly use malicious RTF documents, either delivered directly or loaded through another Office document using remote templates or Word's altChunk feature. Microsoft released a security update in November 2017. This vulnerability is distinct from CVE-2017-11884.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution in the current user's security context, compromising data and functionality accessible to that account. Exploitation under an administrator account can enable full system control, including installing programs, modifying or deleting data, and creating accounts. Observed campaigns have used the vulnerability to deploy information stealers and remote-access malware, including Agent Tesla, FormBook, Remcos, XLoader, and PortDoor. Persistence, credential theft, and surveillance are capabilities of subsequent payloads rather than intrinsic effects of the vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Until remediation is complete, disable the legacy Microsoft Equation Editor COM component using Microsoft's documented registry-based workaround. EMET or Windows Defender Exploit Guard protections for Equation Editor, or system-wide ASLR, can impede known exploitation techniques but should not replace patching. Use non-administrative accounts for document handling, block exploit-bearing attachments with email and endpoint security controls, and verify unexpected documents with senders through known communication channels. Monitor Office document activity followed by unusual script-interpreter execution.
Remediation
Patch, then assume compromise.
Apply Microsoft's security updates addressing CVE-2017-11882 to every affected Office installation. Microsoft initially released the fix in November 2017. Verify that the installed Office version and architecture have received the applicable update; where necessary, upgrade to a supported, patched Office release.
Exploits
12 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2017-11882 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2017-11882?
- Yes. Mallory tracks 12 public exploits or proofs of concept for CVE-2017-11882, the earliest disclosed Nov 15, 2017.
- Is there a patch for CVE-2017-11882?
- Apply Microsoft's security updates addressing CVE-2017-11882 to every affected Office installation. Microsoft initially released the fix in November 2017.
- What products are affected by CVE-2017-11882?
- Microsoft Corporation Microsoft Office.
- How severe is CVE-2017-11882?
- CVE-2017-11882 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 99.9% (100th percentile) as of Nov 17, 2026.
Recent activity
285 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.