CVE-2017-0028

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 19%CVSS: 9.8Exploit: NoneExposed: 0

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

A remote code execution vulnerability exists when Microsoft scripting engine improperly accesses objects in memory. The vulnerability could corrupt memory in a way that enables an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user, aka "Scripting Engine Memory Corruption Vulnerability."

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
97.0%
KEV
Not listed

Published

July 17, 2017

Last Modified

May 13, 2026

Advisory Details (1)

Auto-updated May 16, 2026
No patch confirmed yet.
generic

[CVE-2017-0028] Fix binding of 'async' identifier in the presence of … · chakra-core/ChakraCore@402f3d9 · GitHub

https://github.com/Microsoft/ChakraCore/commit/402f3d967c0a905ec5b9ca9c240783d3f2c15724

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-29 14:03 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-22 14:23 UTCEPSS rescore
  17. 2026-06-21 14:54 UTCEPSS rescore
  18. 2026-06-21 14:54 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-19 16:55 UTCOSV refresh
  22. 2026-06-18 17:50 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
Show 58 more
  1. 2026-06-16 17:50 UTCEPSS rescore
  2. 2026-06-15 17:45 UTCEPSS rescore
  3. 2026-06-14 23:14 UTCEPSS rescore
  4. 2026-06-14 23:14 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-13 22:57 UTCEPSS rescore
  7. 2026-06-12 23:09 UTCEPSS rescore
  8. 2026-06-11 13:57 UTCEPSS rescore
  9. 2026-06-08 14:14 UTCEPSS rescore
  10. 2026-06-07 15:22 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-05 22:44 UTCEPSS rescore
  15. 2026-06-04 13:10 UTCEPSS rescore
  16. 2026-06-04 13:10 UTCEPSS rescore
  17. 2026-06-02 20:10 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 00:14 UTCEPSS rescore
  23. 2026-05-30 22:53 UTCOSV refresh
  24. 2026-05-29 13:41 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-27 13:38 UTCEPSS rescore
  28. 2026-05-27 13:38 UTCEPSS rescore
  29. 2026-05-26 07:17 UTCEPSS rescore
  30. 2026-05-24 16:44 UTCEPSS rescore
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 22:37 UTCEPSS rescore
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-20 11:21 UTCEPSS rescore
  36. 2026-05-20 11:21 UTCEPSS rescore
  37. 2026-05-20 09:03 UTCEG score recompute
  38. 2026-05-20 09:03 UTCGHSA enrichment
  39. 2026-05-20 05:15 UTCEG score recompute
  40. 2026-05-20 05:15 UTCGHSA enrichment
  41. 2026-05-20 01:27 UTCEG score recompute
  42. 2026-05-20 01:27 UTCGHSA enrichment
  43. 2026-05-19 21:39 UTCEG score recompute
  44. 2026-05-19 21:39 UTCGHSA enrichment
  45. 2026-05-19 17:51 UTCEG score recompute
  46. 2026-05-19 17:51 UTCGHSA enrichment
  47. 2026-05-19 14:03 UTCEG score recompute
  48. 2026-05-19 14:03 UTCGHSA enrichment
  49. 2026-05-19 10:15 UTCEG score recompute
  50. 2026-05-19 10:15 UTCGHSA enrichment
  51. 2026-05-19 06:28 UTCEG score recompute
  52. 2026-05-19 06:27 UTCGHSA enrichment
  53. 2026-05-19 02:40 UTCEG score recompute
  54. 2026-05-19 02:40 UTCGHSA enrichment
  55. 2026-05-18 22:51 UTCEG score recompute
  56. 2026-05-18 21:30 UTCEPSS rescore
  57. 2026-05-18 21:30 UTCEPSS rescore
  58. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-0028?
CVE-2017-0028 is a critical vulnerability published on July 17, 2017. A remote code execution vulnerability exists when Microsoft scripting engine improperly accesses objects in memory. The vulnerability could corrupt memory in a way that enables an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the…
When was CVE-2017-0028 disclosed?
CVE-2017-0028 was first published in the National Vulnerability Database on July 17, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0028 actively exploited?
CVE-2017-0028 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0028?
CVE-2017-0028 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-0028?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0028, 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-0028

Explore →

Is Your Infrastructure Affected by CVE-2017-0028?

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

Start Free Scan →Browse All CVEs