CVE-2017-11826

CRITICALNVD 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
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 81%CVSS: 7.8Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed: 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)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
81%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

October 13, 2017

Last Modified

June 17, 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 82× in last 7d / 349× 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 1,173 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2017-11826?
CVE-2017-11826 is a critical 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 June 17, 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