← Vulnerability feed

Vulnerability record · CVE-2016-7190 · published 14 October 2016

CVE-2016-7190: Microsoft Edge Chakra engine memory corruption RCE

Microsoft · Edge

The Chakra JavaScript engine in Microsoft Edge has a memory corruption flaw (CWE-119) that a crafted web site can trigger. Successful exploitation allows arbitrary code execution or a denial of service. It is one of several similar scripting engine memory corruption bugs patched in the same cycle.

7.5 CVSS 3.0 High EPSS 67% · top 0.7% CWE-119 · Memory buffer overflow
7.5CVSS 3.0 base score, v2 7.6
67%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
6References
17 Jun 2026Last modified by NVD

Description

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-3386, CVE-2016-3389, and CVE-2016-7194.

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 19 September 2026. Confidence: medium.

high priorityRemote code execution in a browser engine with a high EPSS score, though exploitation requires user interaction and no KEV listing exists.

What it is

The Chakra JavaScript engine in Microsoft Edge has a memory corruption flaw (CWE-119) that a crafted web site can trigger. Successful exploitation allows arbitrary code execution or a denial of service. It is one of several similar scripting engine memory corruption bugs patched in the same cycle.

Impact

An attacker can run arbitrary code in the context of the Edge process, or crash the browser. Code execution would inherit the user's privileges.

Attack surface

Reached over the network by a user visiting a crafted web site; no authentication is required but user interaction (browsing to the page) is needed per the CVSS vector (AV:N/AC:H/PR:N/UI:R).

Exploitation

Not listed in CISA KEV and no reference tags indicate public exploit code, but EPSS is high (0.669, 99.3rd percentile), suggesting elevated real-world exploitation likelihood.

What to do

  • Apply Microsoft security update MS16-119 (October 2016) to affected Edge/Windows systems.
  • Prioritize patching on internet-facing or browsing-heavy endpoints.
  • Keep Edge and the underlying OS at current supported patch levels.
  • Reduce exposure by restricting untrusted web browsing where feasible.

Detection

  • Monitor for Edge (MicrosoftEdge.exe) crashes consistent with memory corruption.
  • Hunt for suspicious child processes spawned by Edge, such as script interpreters or shells.
  • Review proxy/web logs for known exploit-hosting or malvertising domains.
  • Correlate endpoint telemetry for anomalous code execution originating from the browser process.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2016-7190 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

9.8CVE-2015-0313Adobe Flash Player use-after-free allows remote code executionAdobe Flash Player contains a use-after-free (CWE-416) flaw reachable through unspecified vectors. It affects Flash Player before 13.0.0.269 and 14.x…KEVEPSS 95%analysed9.8CVE-2015-0311Adobe Flash Player unspecified flaw allows remote code executionCVE-2015-0311 is an unspecified vulnerability in Adobe Flash Player affecting versions through 13.0.0.262, 14.x, 15.x, and 16.x through 16.0.0.287 on…KEVEPSS 86%analysed9.6CVE-2024-7971Google Chrome V8 type confusion enables heap corruptionChrome's V8 JavaScript engine contains a type confusion flaw (CWE-843) that lets a crafted HTML page corrupt the heap. It affects Chrome before 128.0…KEVEPSS 21%analysed9.6CVE-2022-4135Google Chrome GPU heap buffer overflow enables sandbox escapeChrome's GPU component contains a heap buffer overflow (CWE-787) fixed in version 107.0.5304.121. An attacker who already controls the renderer proce…KEVEPSS 32%analysed8.8CVE-2023-5217libvpx VP8 encoding heap buffer overflow exploited via crafted HTMLA heap buffer overflow in the VP8 encoder in libvpx affects Google Chrome before 117.0.5938.132 and libvpx 1.13.1, and is reachable through a crafted…KEVEPSS 49%analysed8.8CVE-2021-26411Microsoft Internet Explorer and Edge use-after-free memory corruptionCVE-2021-26411 is a use-after-free (CWE-416) memory corruption flaw in Microsoft Internet Explorer, with Microsoft Edge also listed as an affected pr…KEVEPSS 81%analysed8.8CVE-2020-16009Google Chrome V8 type confusion leads to heap corruptionGoogle Chrome before 86.0.4240.183 contains an inappropriate implementation in the V8 JavaScript engine that allows heap corruption via a crafted HTM…KEVEPSS 48%analysed8.8CVE-2016-7201Microsoft Edge Chakra engine type confusion memory corruptionThe Chakra JavaScript engine in Microsoft Edge mishandles objects in a way that causes type confusion, leading to memory corruption. A crafted web pa…KEVEPSS 80%analysed

Source: NIST National Vulnerability Database (record CVE-2016-7190), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.