CVE-2017-0223

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 36.0%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, 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: 15%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 in Microsoft Chakra Core in the way JavaScript engines render when handling objects in memory. aka "Scripting Engine Memory Corruption Vulnerability". This vulnerability is unique from CVE-2017-0252.

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

Published

May 15, 2017

Last Modified

May 13, 2026

Advisory Details (2)

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

17-05 ChakraCore servicing release by rajatd · Pull Request #2959 · chakra-core/ChakraCore · GitHub

https://github.com/Microsoft/ChakraCore/pull/2959
generic
http://www.securitytracker.com/id/1038425

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Microsoft.ChakraCore1.2.0 ... 1.4.3 (12 versions)1.4.4—

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 6× in last 7d / 27× 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-05 02:27 UTCEPSS rescore
  3. 2026-07-04 06:28 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-28 04:53 UTCEPSS rescore
  8. 2026-06-27 03:05 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-22 14:23 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-18 17:50 UTCEPSS rescore
  16. 2026-06-18 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-14 23:14 UTCEPSS rescore
  23. 2026-06-13 22:57 UTCEPSS rescore
  24. 2026-06-13 22:57 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
Show 51 more
  1. 2026-06-11 13:57 UTCEPSS rescore
  2. 2026-06-08 14:14 UTCEPSS rescore
  3. 2026-06-07 15:22 UTCEPSS rescore
  4. 2026-06-07 15:22 UTCEPSS rescore
  5. 2026-06-06 13:45 UTCEPSS rescore
  6. 2026-06-06 13:45 UTCEPSS rescore
  7. 2026-06-05 22:44 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-06-04 13:10 UTCEPSS rescore
  11. 2026-06-04 13:10 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 22:28 UTCEPSS rescore
  15. 2026-05-31 00:14 UTCEPSS rescore
  16. 2026-05-29 13:41 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-27 13:38 UTCEPSS rescore
  20. 2026-05-27 13:38 UTCEPSS rescore
  21. 2026-05-26 07:17 UTCEPSS rescore
  22. 2026-05-23 00:10 UTCEG score recompute
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-20 22:37 UTCEPSS rescore
  25. 2026-05-20 22:37 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 11:21 UTCEPSS rescore
  28. 2026-05-20 11:21 UTCEPSS rescore
  29. 2026-05-20 10:28 UTCEG score recompute
  30. 2026-05-20 10:28 UTCVendor advisory
  31. 2026-05-20 06:37 UTCEG score recompute
  32. 2026-05-20 06:37 UTCVendor advisory
  33. 2026-05-20 02:46 UTCEG score recompute
  34. 2026-05-20 02:46 UTCVendor advisory
  35. 2026-05-19 22:55 UTCEG score recompute
  36. 2026-05-19 22:55 UTCVendor advisory
  37. 2026-05-19 19:05 UTCEG score recompute
  38. 2026-05-19 19:05 UTCVendor advisory
  39. 2026-05-19 15:14 UTCEG score recompute
  40. 2026-05-19 15:14 UTCVendor advisory
  41. 2026-05-19 11:23 UTCEG score recompute
  42. 2026-05-19 11:23 UTCVendor advisory
  43. 2026-05-19 07:30 UTCEG score recompute
  44. 2026-05-19 07:30 UTCVendor advisory
  45. 2026-05-19 03:39 UTCEG score recompute
  46. 2026-05-19 03:39 UTCVendor advisory
  47. 2026-05-18 23:48 UTCEG score recompute
  48. 2026-05-18 23:48 UTCVendor advisory
  49. 2026-05-18 21:30 UTCEPSS rescore
  50. 2026-05-18 21:30 UTCEPSS rescore
  51. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-0223?
CVE-2017-0223 is a critical vulnerability published on May 15, 2017. A remote code execution vulnerability exists in Microsoft Chakra Core in the way JavaScript engines render when handling objects in memory. aka "Scripting Engine Memory Corruption Vulnerability". This vulnerability is unique from CVE-2017-0252.
When was CVE-2017-0223 disclosed?
CVE-2017-0223 was first published in the National Vulnerability Database on May 15, 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-0223 actively exploited?
CVE-2017-0223 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0223?
CVE-2017-0223 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-0223?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0223, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-0223

Explore →

Is Your Infrastructure Affected by CVE-2017-0223?

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

Start Free Scan →Browse All CVEs