CVE-2018-8629 in the critical feed json
ChakraCore RCE Vulnerability
published 2018-12-12 7 y ago modified 2026-06-17 4 mo ago also GHSA-w9rv-wwxr-vc3q , EUVD-2022-5543
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.6%
- EPSS 22.6% 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-8583, CVE-2018-8617, CVE-2018-8618, CVE-2018-8624.
Patch / fix
- nuget Microsoft.ChakraCore 1.11.4
Exploit prediction
22.60% 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.11.4 |
1.11.4 |
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-8629
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/5869
web
-
github.com
/chakra-core/ChakraCore/commit/69a259c8c3993b23a9e33772fc5a5bfd22466bd5
web
-
securityfocus.com
/bid/106115
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8629
advisory
-
web.archive.org
/web/20210124222857/http://www.securityfocus.com/bid/106115
web
Sources
- CVE List CVE-2018-8629
- GitHub Advisory GHSA-w9rv-wwxr-vc3q
- NVD CVE-2018-8629
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.