CVE-2017-11826

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 2022-03-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: 82%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 2010, SharePoint Enterprise Server 2010, SharePoint Server 2010, Web Applications, Office Web Apps Server 2010 and 2013, Word Viewer, Word 2007, 2010, 2013 and 2016, Word Automation Services, and Office Online Server allow remote code execution when the software fails to properly handle objects in memory.

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

Published

October 13, 2017

Last Modified

April 22, 2026

Advisory Details (5)

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-11826
generic🟡 PoC Available

0patch Blog: 0patching a Pretty Nasty Microsoft Word Type Confusion Vulnerability (CVE-2017-11826)

https://0patch.blogspot.com/2017/11/0patching-pretty-nasty-microsoft-word.html
generic
http://www.securitytracker.com/id/1039541
generic
http://www.securityfocus.com/bid/101219
generic

Exploiting Word: CVE-2017-11826 | Tarlogic

https://www.tarlogic.com/en/blog/exploiting-word-cve-2017-11826/

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 122× in last 7d / 506× 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 678 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCthatskriptkid/CVE-2017-11826
    First seen Feb 9, 2018

    Exploit for CVE-2017-11826

    Open source ↗

Frequently asked(6)

What is CVE-2017-11826?
CVE-2017-11826 is a high vulnerability published on October 13, 2017. Microsoft Office 2010, SharePoint Enterprise Server 2010, SharePoint Server 2010, Web Applications, Office Web Apps Server 2010 and 2013, Word Viewer, Word 2007, 2010, 2013 and 2016, Word Automation Services, and Office Online Server allow remote code execution when the software fails to properly…
When was CVE-2017-11826 disclosed?
CVE-2017-11826 was first published in the National Vulnerability Database on October 13, 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-11826 actively exploited?
Yes. CISA added CVE-2017-11826 to the Known Exploited Vulnerabilities catalog on March 3, 2022, 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-11826?
CVE-2017-11826 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-11826?
CVE-2017-11826 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-11826?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-11826, 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-11826

Explore →

Is Your Infrastructure Affected by CVE-2017-11826?

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

Start Free Scan →Browse All CVEs