CVE-2017-0262

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-02-10), 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 highExposed services: Not assessed

A fix is available — apply it.

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-0261 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 available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
81%
EPSS %ILE
99th
KEV
⚠ Exploited

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

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

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 (3)

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-0262
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-0262
generic
http://www.securityfocus.com/bid/98279

Vendor Advisories for CVE-2017-0262(1)

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

Data Freshness Timeline

(refreshed 83× in last 7d / 359× 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,491 total refreshes for this CVE.

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

Frequently asked(6)

What is CVE-2017-0262?
CVE-2017-0262 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-0261 and CVE-2017-0281.
When was CVE-2017-0262 disclosed?
CVE-2017-0262 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-0262 actively exploited?
Yes. CISA added CVE-2017-0262 to the Known Exploited Vulnerabilities catalog on February 10, 2022, affecting Microsoft Office. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2017-0262?
CVE-2017-0262 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-0262?
CVE-2017-0262 affects Microsoft Office.
How do I remediate CVE-2017-0262?
A fix for CVE-2017-0262 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0262 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-0262?

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

Book a Demo →Browse All CVEs