CVE-2017-0261

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 — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 78%CVSS: 7.8Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
78%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 12, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Fix referenced — no release confirmed yet. Sources: microsoft, cisa.
cisa🔴 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
microsoftMentions a patch (unverified)

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

Vendor Advisories for CVE-2017-0261(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 96× in last 7d / 410× 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,732 total refreshes for this CVE.

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

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 CWE)

Frequently asked(6)

What is CVE-2017-0261?
CVE-2017-0261 is a critical 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 on May 12, 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-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 attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
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 (CRITICAL).
Which products are affected by CVE-2017-0261?
CVE-2017-0261 affects Microsoft Office.
How do I remediate CVE-2017-0261?
A fix for CVE-2017-0261 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2017-0261 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs