CVE-2017-0262

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-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
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 81%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-0261 and CVE-2017-0281.

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

Published

May 12, 2017

Last Modified

April 22, 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

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 / 507× 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 679 total refreshes for this CVE.

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

Frequently asked(6)

What is CVE-2017-0262?
CVE-2017-0262 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-0261 and CVE-2017-0281.
When was CVE-2017-0262 disclosed?
CVE-2017-0262 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-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 patching attention.
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.
Which products are affected by CVE-2017-0262?
CVE-2017-0262 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-0262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0262, 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-0262

Explore →

Is Your Infrastructure Affected by CVE-2017-0262?

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

Start Free Scan →Browse All CVEs