CVE-2017-0210

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

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 8.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
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 20%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An elevation of privilege vulnerability exists when Internet Explorer does not properly enforce cross-domain policies, which could allow an attacker to access information from one domain and inject it into another domain, aka "Internet Explorer Elevation of Privilege Vulnerability."

CVSS v3
8.8
EG Score
9.0(high)
EPSS
97.0%
KEV
⚠ Exploited

Published

April 12, 2017

Last Modified

April 22, 2026

Advisory Details (3)

Auto-updated May 2, 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-0210
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-0210
generic
http://www.securityfocus.com/bid/97512

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 131× in last 7d / 553× 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 738 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(6)

What is CVE-2017-0210?
CVE-2017-0210 is a high vulnerability published on April 12, 2017. An elevation of privilege vulnerability exists when Internet Explorer does not properly enforce cross-domain policies, which could allow an attacker to access information from one domain and inject it into another domain, aka "Internet Explorer Elevation of Privilege Vulnerability."
When was CVE-2017-0210 disclosed?
CVE-2017-0210 was first published in the National Vulnerability Database on April 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-0210 actively exploited?
Yes. CISA added CVE-2017-0210 to the Known Exploited Vulnerabilities catalog on May 24, 2022, affecting Microsoft Internet Explorer. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2017-0210?
CVE-2017-0210 has a CVSS v3 base score of 8.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-0210?
CVE-2017-0210 affects Microsoft Internet Explorer. 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-0210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0210, 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-0210

Explore →

Is Your Infrastructure Affected by CVE-2017-0210?

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

Start Free Scan →Browse All CVEs