CVE-2017-0022

CRITICALNVD 6.59.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-05-24), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.5 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 6.5 MEDIUM under NVD CVSS v3. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2017-0389 (ENISA EUVD) · GHSA-r6m8-274g-vhp5 (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 every mission impact level
CISA-KEV: ExploitedEPSS PROB: 18%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; Windows 7 SP1; Windows 8.1; Windows RT 8.1; Windows Server 2008 SP2 and R2 SP1; Windows Server 2012 Gold and R2; Windows Server 2016; and Windows Vista SP2 improperly handles objects in memory, allowing attackers to test for files on disk via a crafted web site, aka "Microsoft XML Information Disclosure Vulnerability."

CVSS v3
6.5
EG Score
9.0CRITICALhigh confidence
EG Risk
69
EG Risk 69/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 or medium mission impact and sooner than that at high.
EPSS PROB
18%
EPSS %ILE
97th
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 6.5 MEDIUM.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
18% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days 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 or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)14 days 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 partial (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-0022

Published

March 17, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Nov 2, 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-0022
Microsoft

Security Update Guide - Microsoft Security Response Center

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

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/96069
Web page

0patch Blog: Exploit Kit Rendezvous and CVE-2017-0022

https://0patch.blogspot.com/2017/09/exploit-kit-rendezvous-and-cve-2017-0022.html

Vendor Advisories for CVE-2017-0022(1)

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

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 195× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 1,887 refreshes 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,787 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(6)

What is CVE-2017-0022?
CVE-2017-0022 is a critical-severity vulnerability; its CVE record was published on March 17, 2017. Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; Windows 7 SP1; Windows 8.1; Windows RT 8.1; Windows Server 2008 SP2 and R2 SP1; Windows Server 2012 Gold and R2; Windows Server 2016; and Windows Vista SP2 improperly handles objects in memory, allowing attackers to test for…
When was CVE-2017-0022 made public?
CVE-2017-0022 was made public on March 14, 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 March 17, 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-0022 actively exploited?
Yes. CISA added CVE-2017-0022 to the Known Exploited Vulnerabilities catalog on May 24, 2022, affecting Microsoft XML Core Services. 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-0022?
CVE-2017-0022 has a CVSS v3 base score of 6.5 (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-0022?
CVE-2017-0022 affects Microsoft XML Core Services.
How do I remediate CVE-2017-0022?
A fix for CVE-2017-0022 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0022 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-0022?

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