CVE-2017-0262

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2017-0618 (ENISA EUVD) · GHSA-vmqq-f768-gx47 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 81%CVSS: 7.8Exploit: No code on recordExposed 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
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
81% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2017-0262

Published

May 12, 2017

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Nov 16, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa, microsoft.
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-0262
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0262
Web page

PSIRT.COM — Product Security Incident Response Team

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 13× in last 7d / 58× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 1,704 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,604 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:45 UTCEchelonGraph re-scored
  2. 2026-11-21 16:45 UTCVendor advisory
  3. 2026-11-21 16:45 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-11-20 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
  5. 2026-11-20 14:34 UTCEchelonGraph re-scored
  6. 2026-11-20 14:34 UTCVendor advisory
  7. 2026-11-20 14:34 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-19 12:23 UTCEchelonGraph re-scored
  9. 2026-11-19 12:23 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-11-18 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  11. 2026-11-18 10:12 UTCEchelonGraph re-scored
  12. 2026-11-18 10:12 UTCVendor advisory
  13. 2026-11-18 10:12 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-11-17 07:54 UTCEchelonGraph re-scored
  15. 2026-11-17 07:54 UTCVendor advisory
  16. 2026-11-17 07:54 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-11-16 05:42 UTCEchelonGraph re-scored
  18. 2026-11-16 05:42 UTCVendor advisory
  19. 2026-11-16 05:42 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-11-15 03:30 UTCEchelonGraph re-scored
  21. 2026-11-15 03:30 UTCVendor advisory
  22. 2026-11-15 03:30 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-11-14 01:19 UTCEchelonGraph re-scored
  24. 2026-11-14 01:19 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-11-13 16:36 UTCEPSS rescoreEPSS 81% · 99th percentile
Show 75 more
  1. 2026-11-12 23:03 UTCEchelonGraph re-scored
  2. 2026-11-12 23:03 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-12 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  4. 2026-11-11 20:51 UTCEchelonGraph re-scored
  5. 2026-11-11 20:51 UTCVendor advisory
  6. 2026-11-11 20:51 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-11 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
  8. 2026-11-10 18:40 UTCEchelonGraph re-scored
  9. 2026-11-10 18:40 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-11-10 16:30 UTCEPSS rescoreEPSS 81% · 99th percentile
  11. 2026-11-09 16:29 UTCEchelonGraph re-scored
  12. 2026-11-09 16:29 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-11-08 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
  14. 2026-11-08 14:17 UTCEchelonGraph re-scored
  15. 2026-11-08 14:17 UTCVendor advisory
  16. 2026-11-08 14:17 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-11-07 12:06 UTCEchelonGraph re-scored
  18. 2026-11-07 12:06 UTCVendor advisory
  19. 2026-11-07 12:06 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-11-06 09:53 UTCEchelonGraph re-scored
  21. 2026-11-06 09:53 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-11-05 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  23. 2026-11-05 07:42 UTCEchelonGraph re-scored
  24. 2026-11-05 07:42 UTCVendor advisory
  25. 2026-11-05 07:42 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-11-04 05:31 UTCEchelonGraph re-scored
  27. 2026-11-04 05:31 UTCVendor advisory
  28. 2026-11-04 05:31 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-11-03 16:33 UTCEPSS rescoreEPSS 81% · 99th percentile
  30. 2026-11-03 03:20 UTCEchelonGraph re-scored
  31. 2026-11-03 03:20 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-11-02 01:08 UTCEchelonGraph re-scored
  33. 2026-11-02 01:08 UTCVendor advisory
  34. 2026-11-02 01:08 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-31 22:54 UTCEchelonGraph re-scored
  36. 2026-10-31 22:54 UTCVendor advisory
  37. 2026-10-31 22:54 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-10-31 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  39. 2026-10-30 20:43 UTCEchelonGraph re-scored
  40. 2026-10-30 20:43 UTCVendor advisory
  41. 2026-10-30 20:43 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-29 18:32 UTCEchelonGraph re-scored
  43. 2026-10-29 18:32 UTCVendor advisory
  44. 2026-10-29 18:32 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-10-29 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  46. 2026-10-28 16:20 UTCEchelonGraph re-scored
  47. 2026-10-28 16:20 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-27 16:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  49. 2026-10-27 14:09 UTCEchelonGraph re-scored
  50. 2026-10-27 14:08 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-10-26 16:26 UTCEPSS rescoreEPSS 81% · 99th percentile
  52. 2026-10-26 11:56 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-10-25 19:42 UTCEchelonGraph re-scored
  54. 2026-10-25 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  55. 2026-10-25 09:43 UTCEchelonGraph re-scored
  56. 2026-10-25 09:43 UTCVendor advisory
  57. 2026-10-25 09:43 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-10-24 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  59. 2026-10-24 07:31 UTCEchelonGraph re-scored
  60. 2026-10-24 07:31 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-10-23 05:20 UTCEchelonGraph re-scored
  62. 2026-10-23 05:20 UTCVendor advisory
  63. 2026-10-23 05:20 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-10-22 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  65. 2026-10-22 03:07 UTCEchelonGraph re-scored
  66. 2026-10-22 03:07 UTCVendor advisory
  67. 2026-10-22 03:07 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-10-21 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  69. 2026-10-21 00:55 UTCEchelonGraph re-scored
  70. 2026-10-21 00:55 UTCVendor advisory
  71. 2026-10-21 00:55 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-10-20 16:27 UTCEPSS rescoreEPSS 81% · 99th percentile
  73. 2026-10-19 22:42 UTCEchelonGraph re-scored
  74. 2026-10-19 22:42 UTCVendor advisory
  75. 2026-10-19 22:42 UTCGHSA enrichmentGHSA-vmqq-f768-gx47 · GitHub severity HIGH · GitHub CVSS 7.8

Frequently asked(6)

What is CVE-2017-0262?
CVE-2017-0262 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2017-0262 was made public on May 9, 2017: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on May 12, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
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.