How severe is CVE-2017-11882?

CVE-2017-11882 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2017-11882?

CVE-2017-11882 affects the following products: microsoft office.

How do I patch CVE-2017-11882?

No patch has shipped for CVE-2017-11882 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2017-11882 across my infrastructure?

Inventory every microsoft office deployment and check each version against the affected-products list above.

How do I mitigate CVE-2017-11882 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2017-11882 actively exploited in the wild?

Yes. There are 43 known exploit references for CVE-2017-11882, including 1 documented proof-of-concept exploit on Exploit-DB and 29 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-11882?

CVE-2017-11882 has an EPSS (Exploit Prediction Scoring System) score of 99.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-11882 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-11882 (Microsoft Office Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-11882?

CVE-2017-11882 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2017-11882?

CVE-2017-11882 affects microsoft office (4 versions, e.g. 2007, 2010, 2013…). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2017-11882?

A Metasploit module references CVE-2017-11882, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-11882 published, and has it been updated?

CVE-2017-11882 was published on November 15, 2017 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2017-11882 — OFFICE

HIGH

CVE-2017-11882 is a high-severity (CVSS 7.8) Buffer Overflow vulnerability in microsoft office. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) and has been used in ransomware campaigns — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Nov 15, 2017

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

43 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-05-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-11882.

EPSS Exploitation Probability

via FIRST.org ↗

99.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-11882 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

1 product · 4 configurations

Application

officemicrosoft

4 versions

2007201020132016

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-43163remotewindows

Microsoft Office - OLE Remote Code Execution

by embedi · Nov 20, 2017

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft office deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2017-11882 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2017-11882 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works