CVE-2019-0861 in the critical feed json
ChakraCore Memory Corruption Vulnerability
published 2019-04-09 7 y ago modified 2026-06-17 4 mo ago also GHSA-qxmj-3c5h-546c , EUVD-2022-5061
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.1%
- EPSS 11.1% chance of exploitation in 30 days, percentile 95%
- 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-0810, CVE-2019-0812, CVE-2019-0829, CVE-2019-0860.
Patch / fix
- nuget Microsoft.ChakraCore 1.11.8
- microsoft chakracore 1.11.8
Exploit prediction
11.11% chance of exploitation in the next 30 days, higher than 95% 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.8 |
1.11.8 |
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-2019-0861
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/6087
web
-
github.com
/chakra-core/ChakraCore/commit/b481337f2ae6e92efd919692c6691996947f49ec
web
-
securityfocus.com
/bid/107724
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-0861
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210125022152/http://www.securityfocus.com/bid/107724
web
Sources
- CVE List CVE-2019-0861
- GitHub Advisory GHSA-qxmj-3c5h-546c
- NVD CVE-2019-0861
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.