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-7202, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.
CVE-2016-7201
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 80%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
November 10, 2016
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated May 2, 2026Microsoft Edge (Windows 10) - 'chakra.dll' Information Leak / Type Confusion Remote Code Execution - Windows remote Exploit
https://www.exploit-db.com/exploits/40990/Microsoft Edge - 'FillFromPrototypes' Type Confusion - Windows dos Exploit
https://www.exploit-db.com/exploits/40784/GitHub - theori-io/chakra-2016-11: Proof-of-Concept exploit for Edge bugs (CVE-2016-7200 & CVE-2016-7201) · GitHub
https://github.com/theori-io/chakra-2016-11Microsoft Security Bulletin MS16-129 - Critical | Microsoft Learn
https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-129Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| Microsoft.ChakraCore | 1.2.0, 1.2.1 | 1.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 36× in last 7d / 190× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 389 total refreshes for this CVE.
- 2026-07-27 10:53 UTCVendor advisory
- 2026-07-27 06:52 UTCVendor advisory
- 2026-07-27 02:49 UTCVendor advisory
- 2026-07-26 22:46 UTCVendor advisory
- 2026-07-26 18:45 UTCEG score recompute
- 2026-07-26 18:45 UTCVendor advisory
- 2026-07-26 14:50 UTCEPSS rescore
- 2026-07-26 14:42 UTCVendor advisory
- 2026-07-26 10:40 UTCEG score recompute
- 2026-07-26 10:40 UTCVendor advisory
- 2026-07-26 06:36 UTCVendor advisory
- 2026-07-26 02:34 UTCEG score recompute
- 2026-07-26 02:34 UTCVendor advisory
- 2026-07-25 14:13 UTCEPSS rescore
- 2026-07-24 14:13 UTCEPSS rescore
- 2026-07-23 01:24 UTCEG score recompute
- 2026-07-22 21:49 UTCEG score recompute
- 2026-07-22 21:49 UTCVendor advisory
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 17:24 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 13:21 UTCVendor advisory
- 2026-07-22 09:19 UTCVendor advisory
- 2026-07-22 05:18 UTCVendor advisory
- 2026-07-22 01:02 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-21 20:10 UTCVendor advisory
- 2026-07-21 16:09 UTCEG score recompute
- 2026-07-21 16:09 UTCVendor advisory
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:07 UTCVendor advisory
- 2026-07-21 08:03 UTCVendor advisory
- 2026-07-21 04:01 UTCVendor advisory
- 2026-07-20 23:59 UTCVendor advisory
- 2026-07-20 19:58 UTCVendor advisory
- 2026-07-20 07:52 UTCVendor advisory
- 2026-07-20 03:51 UTCVendor advisory
- 2026-07-19 23:49 UTCVendor advisory
- 2026-07-19 19:48 UTCVendor advisory
- 2026-07-19 15:47 UTCVendor advisory
- 2026-07-19 11:44 UTCVendor advisory
- 2026-07-19 07:42 UTCVendor advisory
- 2026-07-19 03:40 UTCEG score recompute
- 2026-07-19 03:40 UTCVendor advisory
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 19:36 UTCVendor advisory
- 2026-07-18 15:34 UTCVendor advisory
- 2026-07-18 11:32 UTCVendor advisory
- 2026-07-18 07:31 UTCVendor advisory
- 2026-07-18 03:29 UTCVendor advisory
- 2026-07-17 23:28 UTCVendor advisory
- 2026-07-17 19:26 UTCVendor advisory
- 2026-07-17 15:23 UTCVendor advisory
- 2026-07-17 11:21 UTCVendor advisory
- 2026-07-17 07:19 UTCEG score recompute
- 2026-07-17 07:19 UTCVendor advisory
- 2026-07-17 03:18 UTCVendor advisory
- 2026-07-16 23:16 UTCVendor advisory
- 2026-07-16 19:15 UTCVendor advisory
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 15:10 UTCVendor advisory
- 2026-07-16 11:08 UTCVendor advisory
- 2026-07-16 07:06 UTCVendor advisory
- 2026-07-15 23:02 UTCVendor advisory
- 2026-07-15 19:00 UTCVendor advisory
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:59 UTCVendor advisory
- 2026-07-15 10:56 UTCVendor advisory
- 2026-07-15 06:53 UTCVendor advisory
- 2026-07-15 02:51 UTCVendor advisory
- 2026-07-14 22:50 UTCVendor advisory
- 2026-07-14 18:45 UTCVendor advisory
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 14:43 UTCVendor advisory
- 2026-07-14 10:39 UTCVendor advisory
- 2026-07-14 06:35 UTCVendor advisory
- 2026-07-14 02:34 UTCVendor advisory
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 06:25 UTCVendor advisory
- 2026-07-13 02:23 UTCVendor advisory
- 2026-07-12 22:22 UTCVendor advisory
- 2026-07-12 18:20 UTCVendor advisory
- 2026-07-12 14:17 UTCVendor advisory
- 2026-07-12 10:15 UTCVendor advisory
- 2026-07-12 06:12 UTCVendor advisory
- 2026-07-12 02:07 UTCVendor advisory
- 2026-07-11 22:06 UTCVendor advisory
- 2026-07-11 18:03 UTCVendor advisory
- 2026-07-11 14:02 UTCVendor advisory
- 2026-07-11 09:58 UTCVendor advisory
- 2026-07-11 08:24 UTCEPSS rescore
- 2026-07-11 05:56 UTCVendor advisory
- 2026-07-11 01:55 UTCVendor advisory
- 2026-07-10 21:51 UTCVendor advisory
Publicly available exploits
(2 references)Working exploit code is in the public domain (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-40990First seen Jan 5, 2017
Microsoft Edge (Windows 10) - 'chakra.dll' Information Leak / Type Confusion Remote Code Execution
Open source ↗ - Exploit-DBEDB-40784✓ verifiedFirst seen Nov 18, 2016
Microsoft Edge - 'FillFromPrototypes' Type Confusion
Open source ↗
Frequently asked(6)
What is CVE-2016-7201?
When was CVE-2016-7201 disclosed?
Is CVE-2016-7201 actively exploited?
What is the CVSS score of CVE-2016-7201?
Which products are affected by CVE-2016-7201?
How do I remediate CVE-2016-7201?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-7201
Is Your Infrastructure Affected by CVE-2016-7201?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.