Vulnerability record · CVE-2016-7203 · published 10 November 2016
CVE-2016-7203: Microsoft Edge Chakra engine memory corruption allows remote code execution
Microsoft · Edge
The Chakra JavaScript engine in Microsoft Edge has a memory corruption flaw (CWE-119) that a crafted website can trigger. It is one of several similar scripting engine memory corruption bugs patched in the same update. Successful exploitation can run arbitrary code in the browser's context or crash the browser.
Description
The Chakra JavaScript scripting 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-7200, CVE-2016-7201, CVE-2016-7202, 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 priorityRemote code execution in a widely deployed browser with public exploit code and very high EPSS, though exploitation requires user interaction and the flaw is dated.
What it is
The Chakra JavaScript engine in Microsoft Edge has a memory corruption flaw (CWE-119) that a crafted website can trigger. It is one of several similar scripting engine memory corruption bugs patched in the same update. Successful exploitation can run arbitrary code in the browser's context or crash the browser.
Impact
An attacker can execute arbitrary code with the privileges of the Edge process, or cause a denial of service through memory corruption. In a browser context this typically means code execution on the victim's machine.
Attack surface
Reached over the network by visiting a malicious or compromised web page that triggers the Chakra engine. No authentication is required, but user interaction (opening the page) is needed per the CVSS vector (AV:N/AC:H/PR:N/UI:R).
Exploitation
Not listed in CISA KEV, but EPSS is high (0.649, 99.2nd percentile) and a public Exploit-DB entry (40787) exists, indicating exploit code is available.
What to do
- Apply Microsoft security update MS16-129 (November 2016) or later to patch Edge and the Chakra engine.
- If patching is delayed, restrict or disable Edge usage and route browsing through a maintained, updated browser.
- Keep Windows and all browser components current; this flaw is part of a batch of Chakra memory corruption issues fixed together.
- Use exploit mitigation features (ASLR, DEP, CFG) and endpoint protection to raise the cost of memory corruption exploitation.
Detection
- Monitor for Edge/Chakra process crashes (msedge.exe) that correlate with visits to untrusted sites.
- Hunt for suspicious child processes spawned by msedge.exe, a common post-exploitation indicator for browser RCE.
- Review proxy and DNS logs for known exploit-hosting domains and drive-by pages delivering Chakra exploits.
- Alert on Exploit-DB 40787 or related PoC signatures in network or endpoint telemetry.
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-7203 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-7203), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.