High

ChakraCore RCE Vulnerability

  • Disclosed: 13.05.2022
  • Updated: 11.10.2026 11:23

Microsoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka "Scripting Engine Security Feature Bypass".

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
.NET (NuGet) Microsoft.ChakraCore < 1.8.0 1.8.0

References

CVSS score 7.5/10
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness (CWE)
-
Platform
.NET (NuGet)
Package
Microsoft.ChakraCore
Disclosed
13.05.2022
Updated
11.10.2026 11:23

Sources and licenses

OSV / GitHub Advisory Database - GHSA-fv8m-p45w-gf38 - CC BY 4.0

Vulnerability history: Microsoft.ChakraCore

All published vulnerabilities of this package (.NET (NuGet)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (247) in the archive
Total entries
247
First → latest
04.2019 05.2022
Without a fix
5
Exploited in attacks
3

Severity breakdown

  • Critical 5
  • High 234
  • Medium 8

Disclosures per year

  1. 2019: 8
  2. 2020: 0
  3. 2021: 58
  4. 2022: 181
  5. 2023: 0
  6. 2024: 0
  7. 2025: 0
  8. 2026: 0
Severity:
  1. High · 7.5 CVE-2020-0813 < 1.11.17 1.11.17
  2. High · 7.5 CVE-2019-1024 < 1.11.10 1.11.10
  3. High · 7.5 CVE-2019-1002 < 1.11.10 1.11.10
  4. High · 7.5 CVE-2019-1051 < 1.11.10 1.11.10
  5. High · 7.5 CVE-2019-1052 < 1.11.10 1.11.10
  6. High · 7.5 CVE-2021-42279 <= 1.11.24 no fix
  7. High · 8.1 CVE-2020-1073 < 1.11.20 1.11.20
  8. High · 7.5 CVE-2020-1065 < 1.11.19 1.11.19
  9. High · 7.5 CVE-2020-1037 < 1.11.19 1.11.19
  10. High · 7.5 CVE-2020-0970 < 1.11.18 1.11.18
  11. High · 7.5 CVE-2020-0969 < 1.11.18 1.11.18
  12. High · 7.5 CVE-2020-0812 < 1.11.17 1.11.17
  13. High · 7.5 CVE-2020-0811 < 1.11.17 1.11.17
  14. High · 7.5 CVE-2020-0767 < 1.11.16 1.11.16
  15. High · 7.5 CVE-2020-0711 < 1.11.16 1.11.16
  16. High · 7.5 CVE-2020-0710 < 1.11.16 1.11.16
  17. High · 7.5 CVE-2020-0712 < 1.11.16 1.11.16
  18. High · 7.5 CVE-2020-0713 < 1.11.16 1.11.16
  19. High · 7.5 CVE-2017-0224 < 1.4.4 1.4.4
  20. High · 7.5 CVE-2017-0235 < 1.4.4 1.4.4
  21. Critical · 9.8 CVE-2017-0252 < 1.4.4 1.4.4
  22. Critical · 9.8 CVE-2017-0223 < 1.4.4 1.4.4
  23. High · 7.5 CVE-2017-0234 < 1.4.4 1.4.4
  24. High · 7.5 CVE-2017-0236 < 1.4.4 1.4.4
  25. Critical · 9.8 CVE-2017-8658 < 1.6.1 1.6.1
  26. High · 7.5 CVE-2017-11797 < 1.7.3 1.7.3
  27. High · 7.5 CVE-2017-11801 < 1.7.3 1.7.3
  28. High · 7.5 CVE-2017-11792 < 1.7.3 1.7.3
  29. High · 7.5 CVE-2017-11821 < 1.7.3 1.7.3
  30. High · 7.5 CVE-2017-11796 < 1.7.3 1.7.3
  31. High · 7.5 CVE-2017-11806 < 1.7.3 1.7.3
  32. High · 7.5 CVE-2017-11805 < 1.7.3 1.7.3
  33. High · 7.5 CVE-2017-11807 < 1.7.3 1.7.3
  34. High · 7.5 CVE-2017-11916 < 1.7.5 1.7.5
  35. High · 7.5 CVE-2017-11908 < 1.7.5 1.7.5
  36. High · 7.5 CVE-2017-11905 < 1.7.5 1.7.5
  37. High · 7.5 CVE-2017-11889 < 1.7.5 1.7.5
  38. High · 8.8 CVE-2016-0024 < 1.2.0 1.2.0
  39. High · 7.5 CVE-2016-0186 < 1.2.0.0 1.2.0.0
  40. High · 7.5 CVE-2016-0193 < 1.2.0.0 1.2.0.0
  41. High · 7.5 CVE-2016-0191 < 1.2.0.0 1.2.0.0
  42. High · 7.5 CVE-2016-3202 < 1.2.0.0 1.2.0.0
  43. High · 8.8 CVE-2016-3199 < 1.2.0.0 1.2.0.0
  44. High · 8.8 CVE-2016-3214 < 1.3.0 1.3.0
  45. High · 8.8 CVE-2016-3248 <= 1.2.0 no fix
  46. High · 8.8 CVE-2016-3260 < 1.2.0.0 1.2.0.0
  47. High · 8.8 CVE-2016-3259 < 1.2.0.0 1.2.0.0
  48. High · 8.8 CVE-2016-3269 < 1.2.0.0 1.2.0.0
  49. High · 8.8 CVE-2016-3265 < 1.2.0.0 1.2.0.0
  50. High · 7.5 CVE-2016-3296 <= 1.2.0 no fix
  51. High · 7.5 CVE-2016-3350 < 1.2.1 1.2.1
  52. High · 7.5 CVE-2016-3377 < 1.2.1 1.2.1
  53. High · 7.5 CVE-2016-3382 < 1.2.1 1.2.1
  54. High · 7.5 CVE-2016-3390 < 1.2.1 1.2.1
  55. High · 7.5 CVE-2016-3386 < 1.2.1 1.2.1
  56. High · 7.5 CVE-2016-3389 < 1.2.1 1.2.1
  57. High · 7.5 CVE-2016-7189 < 1.2.1 1.2.1
  58. High · 7.5 CVE-2016-7194 <= 1.2.1 no fix
  59. High · 7.5 CVE-2016-7190 <= 1.2.1 no fix
  60. High · 7.5 Exploited in attacks CVE-2016-7201 < 1.2.2 1.2.2
  61. High · 7.5 Exploited in attacks CVE-2016-7200 < 1.2.2 1.2.2
  62. High · 7.5 CVE-2016-7202 < 1.2.2 1.2.2
  63. High · 7.5 CVE-2016-7203 < 1.2.2 1.2.2
  64. High · 7.5 CVE-2016-7208 < 1.2.2 1.2.2
  65. High · 7.5 CVE-2016-7240 < 1.2.2 1.2.2
  66. High · 7.5 CVE-2016-7242 < 1.2.2 1.2.2
  67. High · 7.5 CVE-2016-7243 < 1.2.2 1.2.2
  68. High · 7.5 CVE-2017-11909 < 1.7.5 1.7.5
  69. High · 7.5 CVE-2017-11911 < 1.7.5 1.7.5
  70. High · 7.5 CVE-2017-11893 < 1.7.5 1.7.5
  71. High · 7.5 CVE-2018-8145 < 1.8.4 1.8.4
  72. ChakraCore RCE Vulnerability this entry
    High · 7.5 CVE-2018-0818 < 1.8.0 1.8.0
  73. Critical · 9.8 CVE-2017-11767 < 1.6.2 1.6.2
  74. High · 7.5 CVE-2019-0861 < 1.11.8 1.11.8
  75. High · 7.5 CVE-2019-0860 < 1.11.8 1.11.8
Show more (20) Showing 80 of 239

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.