CVE-2017-0261

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: 78%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 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0262 and CVE-2017-0281.

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
99.5%
KEV
⚠ Exploited

Published

May 12, 2017

Last Modified

April 22, 2026

Advisory Details (4)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-0261
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-0261
generic
http://www.securitytracker.com/id/1038444
generic
http://www.securityfocus.com/bid/98104

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 87× in last 7d / 389× 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 715 total refreshes for this CVE.

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

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 PoCkcufId/eps-CVE-2017-0261
    First seen Mar 31, 2019

    eps漏洞(CVE-2017-0261)漏洞分析

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2017-0261?
CVE-2017-0261 is a high vulnerability published on May 12, 2017. Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0262 and CVE-2017-0281.
When was CVE-2017-0261 disclosed?
CVE-2017-0261 was first published in the National Vulnerability Database on May 12, 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-0261 actively exploited?
Yes. CISA added CVE-2017-0261 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-0261?
CVE-2017-0261 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-0261?
CVE-2017-0261 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-0261?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0261, 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-0261

Explore →

Is Your Infrastructure Affected by CVE-2017-0261?

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

Start Free Scan →Browse All CVEs