Live › vulnerability › CVE-2017-11882
Go to dashboardMicrosoft Office has a memory corruption flaw that lets a crafted document run code as the current user. Attackers are actively exploiting it in the wild and it is tied to ransomware campaigns.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply updates per vendor instructions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Microsoft Office | vendor | – | – |
Unknown from the sources. In the analyst’s queue.
Apply the Microsoft Office security update per vendor instructions (CISA required action); the specific patched build is unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1, and Microsoft Office 2016 allow an attacker to run arbitrary code in the context of the current user by failing to properly handle objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11884.
This page as .md · .json · in your agent: get_signal("CVE-2017-11882")
CISA KEV catalog, Creative Commons 0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.