CVE-2017-11882 — Microsoft Office

What is CVE-2017-11882?

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.

The record classifies CVE-2017-11882 under weakness class CWE-119. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 4 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 3286 days ago.

Severity and exploitation probability

CVSS v3.1 base score: 7.8 — HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (FIRST): 99.9% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
CISA KEV: Listed since 2021-11-03, federal remediation deadline 2022-05-03 — used in known ransomware campaigns
Threadlinqs priority: 10/10 — CISA lists it as used in ransomware, which Threadlinqs scores at the maximum
Published: 2017-11-15

Is CVE-2017-11882 being exploited?

CISA added CVE-2017-11882 to the Known Exploited Vulnerabilities catalog on 2021-11-03, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2022-05-03 under BOD 22-01. CISA flags the vulnerability as one used in known ransomware campaigns. Weaponised exploit code for CVE-2017-11882 is publicly available. 11 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 58 in the Threadlinqs vulnerability feed.

Ridter/CVE-2017-11882 (github)
embedi/CVE-2017-11882 (github)
rip1s/CVE-2017-11882 (github)
rxwx/CVE-2018-0802 (github)
Ridter/RTF_11882_0802 (github)
0x09AL/CVE-2017-11882-metasploit (github)
starnightcyber/CVE-2017-11882 (github)
BlackMathIT/2017-11882_Generator (github)

Affected products and versions

Microsoft: Office 2007, Office 2010, Office 2013, Office 2016

How to fix CVE-2017-11882

The record marks a vendor fix as available for CVE-2017-11882. Patch reference: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-11882. Vendor advisory: https://0patch.blogspot.com/2017/11/official-patch-for-cve-2017-11882-meets.html. Because CVE-2017-11882 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2022-05-03. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2017-11882

5 tracked threats in the Threadlinqs corpus reference CVE-2017-11882, either in the campaign’s CVE list or as an indicator on the campaign record.

XLoader (v8.9) infostealer delivered via purchase-order phishing DOCX exploiting CVE-2017-11882 — HIGH · 2026-11-13
Common default passwords used to protect malware-sample archives and encrypted malicious documents (Hexacorn research, incl. Excel VelvetSweatshop) — LOW · 2026-10-24
Q2 2026 Vulnerability and Exploit Landscape: Exploited AI-platform flaws (OpenClaw CVE-2026-25253, Dify CVE-2026-41948, Open WebUI CVE-2026-45386), Exchange CVE-2026-45501, and Linux kernel page-cache LPE exploit wave (Copy Fail, Dirty Frag) — HIGH · 2026-10-20
Agent Tesla .NET Remote Access Trojan — Credential and Data Theft via Keylogging and MaaS Operations — HIGH · 2026-06-23
CVE-2026-21509: Russian Hackers Exploit Microsoft Office Vulnerability Against Ukraine — CRITICAL · 2026-02-03

Sources

Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories.

Vulnerability database entry

Other references

Showing 10 of 14 recorded references.