CVE-2019-0810 in the critical feed json
ChakraCore RCE Vulnerability
published 2019-04-09 7 y ago modified 2026-06-17 4 mo ago also GHSA-2mmc-5phj-4wjj , EUVD-2022-2016
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.5%
- EPSS 11.5% chance of exploitation in 30 days, percentile 96%
- 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 CVE ID is unique from CVE-2019-0806, CVE-2019-0812, CVE-2019-0829, CVE-2019-0860, CVE-2019-0861.
Patch / fix
- nuget Microsoft.ChakraCore 1.11.8
- microsoft chakracore 1.11.8
Exploit prediction
11.53% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/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.8 |
1.11.8 |
Affected products
- Microsoft Microsoft Edge
- Microsoft ChakraCore
Classification
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0810
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/6087
web
-
github.com
/chakra-core/ChakraCore/commit/35ee5053bfc3186da193b9cd85e9a5916580bf80
web
-
zerodayinitiative.com
/advisories/ZDI-19-361/
third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2019-0810
advisory
-
github.com
/chakra-core/ChakraCore
package
-
zerodayinitiative.com
/advisories/ZDI-19-361
web
Sources
- CVE List CVE-2019-0810
- GitHub Advisory GHSA-2mmc-5phj-4wjj
- NVD CVE-2019-0810
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.