Vulnerability record · CVE-2016-7202 · published 10 November 2016
CVE-2016-7202: Microsoft Edge and IE Scripting Engine Memory Corruption
Microsoft · Edge
The scripting engines in Internet Explorer 9 through 11 and Microsoft Edge contain a memory corruption flaw (CWE-119) that a crafted web page can trigger. Successful exploitation allows remote code execution or a denial of service. It is one of several related scripting engine bugs patched in late 2016.
Description
The scripting engines in Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow 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," as demonstrated by the Chakra JavaScript engine, a different vulnerability than CVE-2016-7200, CVE-2016-7201, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Automated analysis
high priorityHigh CVSS (7.5) with public exploit code and very high EPSS, though exploitation requires user interaction and the affected browsers are legacy.
What it is
The scripting engines in Internet Explorer 9 through 11 and Microsoft Edge contain a memory corruption flaw (CWE-119) that a crafted web page can trigger. Successful exploitation allows remote code execution or a denial of service. It is one of several related scripting engine bugs patched in late 2016.
Impact
An attacker can execute arbitrary code in the context of the browser process or crash it, giving code execution on the victim's machine or a denial of service.
Attack surface
Reached over the network via a crafted web site rendered by the affected browser; no authentication is required, but the victim must be convinced to visit the page (user interaction required per the CVSS vector).
Exploitation
Not listed in CISA KEV, but EPSS is very high (0.733, 99.4th percentile) and public Exploit-DB entries (40786, 40793) exist, indicating exploit code is publicly available.
What to do
- Apply Microsoft security updates MS16-129 and MS16-144 to patch the scripting engine.
- Upgrade or migrate off Internet Explorer 9-11 and unsupported Edge versions to a current, supported browser.
- Enforce browser isolation or sandboxing for legacy browser use where patching is not possible.
- Block or restrict access to untrusted web content and disable unnecessary scripting where feasible.
Detection
- Monitor for browser process crashes (iexplore.exe, MicrosoftEdge.exe) that may indicate memory corruption attempts.
- Hunt for exploit artifacts matching public PoCs (Exploit-DB 40786/40793) in proxy or endpoint telemetry.
- Alert on suspicious child processes spawned by the browser, a common post-exploitation indicator.
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-7202 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.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2016-7202), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.