CVE-2017-11826 is a remote code execution vulnerability in multiple Microsoft Office products, including Office 2010, SharePoint Server 2010, Office Web Apps Server 2010 and 2013, Word Viewer, Word 2007-2016, Word Automation Services, and Office Online Server. The vulnerability arises from improper handling of objects in memory, which can be triggered by a specially crafted Office file, leading to arbitrary code execution in the context of the current user.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for CVE-2017-11826, a Microsoft Word vulnerability. The main file, gen_word.py, is a Python script that generates a malicious Word document (demo.docx). The script takes a URL as an argument, which is embedded into a DDEAUTO field in the document. When a victim opens the document in a vulnerable version of Microsoft Word on Windows, the DDEAUTO field triggers the execution of a PowerShell command that downloads a file from the specified URL and executes it. The repository contains only two files: a README.md with a brief description and a reference article, and the exploit generator script. No hardcoded network endpoints are present; the URL is supplied by the user at runtime. The exploit demonstrates the attack vector but does not include a weaponized or customizable payload beyond the download-and-execute mechanism.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.