CVE-2016-0186 in the critical feed json
ChakraCore RCE Vulnerability
published 2016-05-11 10 y ago modified 2026-06-17 4 mo ago also GHSA-fjj8-gv4j-953p , EUVD-2022-3798
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.4%
- EPSS 19.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
The Chakra JavaScript engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," a different vulnerability than CVE-2016-0191 and CVE-2016-0193.
Patch / fix
Exploit prediction
19.45% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
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.2.0.0 |
1.2.0.0 |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/chakra-core/ChakraCore/commit/d21529b131d831fc4470139bfc90d80ae7481fa2
web
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2016/ms16-052
vendor-advisory, web
-
securitytracker.com
/id/1035821
vdb-entry
-
zerodayinitiative.com
/advisories/ZDI-16-338
web
-
securityfocus.com
/bid/90008
vdb-entry
-
zerodayinitiative.com
/advisories/ZDI-16-355
web
-
nvd.nist.gov
/vuln/detail/CVE-2016-0186
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20201024061334/http://www.securitytracker.com/id/1035821
web
-
web.archive.org
/web/20210123133438/http://www.securityfocus.com/bid/90008
web
Sources
- CVE List CVE-2016-0186
- GitHub Advisory GHSA-fjj8-gv4j-953p
- NVD CVE-2016-0186
Fencer Intel 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.