CVE-2018-8227 in the critical feed json
ChakraCore RCE Vulnerability
published 2018-06-14 8 y ago modified 2026-06-17 4 mo ago also GHSA-gqh4-4r89-pr95 , EUVD-2022-3992
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.9%
- EPSS 16.9% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8229.
Patch / fix
- nuget Microsoft.ChakraCore 1.8.5
Exploit prediction
16.91% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.6 | AV:N/AC:H/Au:N/C:C/I:C/A:C |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Microsoft.ChakraCore | <1.8.5 |
1.8.5 |
Affected products
- Microsoft Microsoft Edge
- Microsoft ChakraCore
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8227
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/commit/8af718902bfdc23bdce67d013eb25bd73773e306
web
-
securityfocus.com
/bid/104368
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1041097
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8227
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124174712/http://www.securityfocus.com/bid/104368
web
-
web.archive.org
/web/20210927135934/http://www.securitytracker.com/id/1041097
web
Sources
- CVE List CVE-2018-8227
- GitHub Advisory GHSA-gqh4-4r89-pr95
- NVD CVE-2018-8227
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.