CVE-2017-11882

HIGHNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
9.0(high)
EPSS
100.0%
KEV
⚠ Exploited

Published

November 15, 2017

Last Modified

April 22, 2026

Advisory Details (10)

Auto-updated May 19, 2026
🔬 Proof of concept available. Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-11882
generic

GitHub - rip1s/CVE-2017-11882: CVE-2017-11882 Exploit accepts over 17k bytes long command/code in maximum. · GitHub

https://github.com/unamer/CVE-2017-11882
generic🟡 PoC Available

GitHub - rxwx/CVE-2017-11882: Proof-of-Concept exploits for CVE-2017-11882 · GitHub

https://github.com/rxwx/CVE-2017-11882
generic🟡 PoC Available

GitHub - embedi/CVE-2017-11882: Proof-of-Concept exploits for CVE-2017-11882 · GitHub

https://github.com/embedi/CVE-2017-11882
generic

GitHub - 0x09AL/CVE-2017-11882-metasploit: This is a Metasploit module which exploits CVE-2017-11882 using the POC released here : https://embedi.com/blog/skeleton-closet-ms-office-vulnerability-you-didnt-know-about. · GitHub

https://github.com/0x09AL/CVE-2017-11882-metasploit
generic

0patch Blog: Microsoft's Manual Binary Patch For CVE-2017-11882 Meets 0patch

https://0patch.blogspot.com/2017/11/official-patch-for-cve-2017-11882-meets.html
generic🟡 PoC Available

0patch Blog: Did Microsoft Just Manually Patch Their Equation Editor Executable? Why Yes, Yes They Did. (CVE-2017-11882)

https://0patch.blogspot.com/2017/11/did-microsoft-just-manually-patch-their.html
generic
http://www.securitytracker.com/id/1039783
generic
http://www.securityfocus.com/bid/101757
generic

Logdown - Site Maintenance

http://reversingminds-blog.logdown.com/posts/3907313-fileless-attack-in-word-without-macros-cve-2017-11882

Vendor Advisories for CVE-2017-11882(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 142× in last 7d / 584× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 769 total refreshes for this CVE.

  1. 2026-07-07 17:16 UTCCISA KEV update
  2. 2026-07-07 16:22 UTCEG score recompute
  3. 2026-07-07 16:22 UTCVendor advisory
  4. 2026-07-07 16:22 UTCGHSA enrichment
  5. 2026-07-07 12:39 UTCEG score recompute
  6. 2026-07-07 12:39 UTCVendor advisory
  7. 2026-07-07 12:39 UTCGHSA enrichment
  8. 2026-07-07 08:58 UTCEG score recompute
  9. 2026-07-07 08:58 UTCVendor advisory
  10. 2026-07-07 08:57 UTCGHSA enrichment
  11. 2026-07-07 05:15 UTCEG score recompute
  12. 2026-07-07 05:15 UTCVendor advisory
  13. 2026-07-07 05:15 UTCGHSA enrichment
  14. 2026-07-07 01:34 UTCEG score recompute
  15. 2026-07-07 01:34 UTCVendor advisory
  16. 2026-07-07 01:34 UTCGHSA enrichment
  17. 2026-07-06 21:53 UTCEG score recompute
  18. 2026-07-06 21:53 UTCVendor advisory
  19. 2026-07-06 21:52 UTCGHSA enrichment
  20. 2026-07-06 18:10 UTCEG score recompute
  21. 2026-07-06 18:10 UTCVendor advisory
  22. 2026-07-06 18:10 UTCGHSA enrichment
  23. 2026-07-06 14:28 UTCEG score recompute
  24. 2026-07-06 14:28 UTCVendor advisory
  25. 2026-07-06 14:28 UTCGHSA enrichment
Show 75 more
  1. 2026-07-06 10:46 UTCEG score recompute
  2. 2026-07-06 10:46 UTCVendor advisory
  3. 2026-07-06 10:46 UTCGHSA enrichment
  4. 2026-07-06 06:58 UTCEG score recompute
  5. 2026-07-06 06:58 UTCVendor advisory
  6. 2026-07-06 06:58 UTCGHSA enrichment
  7. 2026-07-06 03:17 UTCEG score recompute
  8. 2026-07-06 03:17 UTCVendor advisory
  9. 2026-07-06 03:17 UTCGHSA enrichment
  10. 2026-07-05 23:36 UTCEG score recompute
  11. 2026-07-05 23:36 UTCVendor advisory
  12. 2026-07-05 23:36 UTCGHSA enrichment
  13. 2026-07-05 19:55 UTCEG score recompute
  14. 2026-07-05 19:55 UTCVendor advisory
  15. 2026-07-05 19:55 UTCGHSA enrichment
  16. 2026-07-05 16:14 UTCEG score recompute
  17. 2026-07-05 16:14 UTCVendor advisory
  18. 2026-07-05 16:14 UTCGHSA enrichment
  19. 2026-07-05 12:31 UTCEG score recompute
  20. 2026-07-05 12:31 UTCVendor advisory
  21. 2026-07-05 12:31 UTCGHSA enrichment
  22. 2026-07-05 08:50 UTCEG score recompute
  23. 2026-07-05 08:50 UTCVendor advisory
  24. 2026-07-05 08:49 UTCGHSA enrichment
  25. 2026-07-05 05:08 UTCEG score recompute
  26. 2026-07-05 05:08 UTCVendor advisory
  27. 2026-07-05 05:07 UTCGHSA enrichment
  28. 2026-07-05 01:24 UTCEG score recompute
  29. 2026-07-05 01:24 UTCVendor advisory
  30. 2026-07-05 01:24 UTCGHSA enrichment
  31. 2026-07-04 21:43 UTCEG score recompute
  32. 2026-07-04 21:43 UTCVendor advisory
  33. 2026-07-04 21:43 UTCGHSA enrichment
  34. 2026-07-04 18:02 UTCEG score recompute
  35. 2026-07-04 18:02 UTCVendor advisory
  36. 2026-07-04 18:02 UTCGHSA enrichment
  37. 2026-07-04 14:18 UTCEG score recompute
  38. 2026-07-04 14:18 UTCVendor advisory
  39. 2026-07-04 14:18 UTCGHSA enrichment
  40. 2026-07-04 10:37 UTCEG score recompute
  41. 2026-07-04 10:37 UTCVendor advisory
  42. 2026-07-04 10:36 UTCGHSA enrichment
  43. 2026-07-04 06:53 UTCEG score recompute
  44. 2026-07-04 06:53 UTCVendor advisory
  45. 2026-07-04 06:53 UTCGHSA enrichment
  46. 2026-07-04 03:11 UTCEG score recompute
  47. 2026-07-04 03:11 UTCVendor advisory
  48. 2026-07-04 03:11 UTCGHSA enrichment
  49. 2026-07-03 23:29 UTCEG score recompute
  50. 2026-07-03 23:29 UTCVendor advisory
  51. 2026-07-03 23:29 UTCGHSA enrichment
  52. 2026-07-03 19:48 UTCEG score recompute
  53. 2026-07-03 19:48 UTCVendor advisory
  54. 2026-07-03 19:48 UTCGHSA enrichment
  55. 2026-07-03 16:07 UTCEG score recompute
  56. 2026-07-03 16:07 UTCVendor advisory
  57. 2026-07-03 16:07 UTCGHSA enrichment
  58. 2026-07-03 12:26 UTCEG score recompute
  59. 2026-07-03 12:26 UTCVendor advisory
  60. 2026-07-03 12:26 UTCGHSA enrichment
  61. 2026-07-03 08:43 UTCEG score recompute
  62. 2026-07-03 08:43 UTCVendor advisory
  63. 2026-07-03 08:43 UTCGHSA enrichment
  64. 2026-07-03 05:02 UTCEG score recompute
  65. 2026-07-03 05:02 UTCVendor advisory
  66. 2026-07-03 05:02 UTCGHSA enrichment
  67. 2026-07-03 01:21 UTCEG score recompute
  68. 2026-07-03 01:21 UTCVendor advisory
  69. 2026-07-03 01:21 UTCGHSA enrichment
  70. 2026-07-02 21:39 UTCEG score recompute
  71. 2026-07-02 21:39 UTCVendor advisory
  72. 2026-07-02 21:39 UTCGHSA enrichment
  73. 2026-07-02 17:58 UTCEG score recompute
  74. 2026-07-02 17:58 UTCVendor advisory
  75. 2026-07-02 17:58 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCRetr0-code/SignHere
    First seen Jan 25, 2021

    SignHere is implementation of CVE-2017-11882. SignHere is builder of malicious rtf document and VBScript payloads.

    Open source ↗
  • GitHub PoClikekabin/CVE-2018-0802_CVE-2017-11882
    First seen Jan 16, 2018
    Open source ↗
  • GitHub PoCRidter/RTF_11882_0802
    First seen Jan 12, 2018

    PoC for CVE-2018-0802 And CVE-2017-11882

    Open source ↗
  • GitHub PoCrxwx/CVE-2018-0802
    First seen Jan 11, 2018

    PoC Exploit for CVE-2018-0802 (and optionally CVE-2017-11882)

    Open source ↗
  • GitHub PoCstarnightcyber/CVE-2017-11882
    First seen Nov 22, 2017

    CVE-2017-11882 exploitation

    Open source ↗
  • GitHub PoCBlackMathIT/2017-11882_Generator
    First seen Nov 21, 2017

    CVE-2017-11882 File Generator PoC

    Open source ↗
  • GitHub PoCrip1s/CVE-2017-11882
    First seen Nov 21, 2017

    CVE-2017-11882 Exploit accepts over 17k bytes long command/code in maximum.

    Open source ↗
  • GitHub PoCRidter/CVE-2017-11882
    First seen Nov 21, 2017

    CVE-2017-11882 from https://github.com/embedi/CVE-2017-11882

    Open source ↗
  • GitHub PoC0x09AL/CVE-2017-11882-metasploit
    First seen Nov 21, 2017

    This is a Metasploit module which exploits CVE-2017-11882 using the POC released here : https://embedi.com/blog/skeleton-closet-ms-office-vulnerability-you-didnt-know-about.

    Open source ↗
  • Exploit-DBEDB-43163
    First seen Nov 20, 2017

    Microsoft Office - OLE Remote Code Execution

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2017-11882?
CVE-2017-11882 is a high vulnerability published on November 15, 2017. 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…
When was CVE-2017-11882 disclosed?
CVE-2017-11882 was first published in the National Vulnerability Database on November 15, 2017, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-11882 actively exploited?
Yes. CISA added CVE-2017-11882 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Office. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2017-11882?
CVE-2017-11882 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2017-11882?
CVE-2017-11882 affects Microsoft Office. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2017-11882?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-11882, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-11882

Explore →

Is Your Infrastructure Affected by CVE-2017-11882?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs