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 56× in last 7d / 210× 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 754 total refreshes for this CVE.
- 2026-09-19 13:47 UTCVendor advisory
- 2026-09-19 09:45 UTCVendor advisory
- 2026-09-19 05:44 UTCVendor advisory
- 2026-09-19 01:42 UTCVendor advisory
- 2026-09-18 21:41 UTCEG score recompute
- 2026-09-18 21:41 UTCVendor advisory
- 2026-09-18 19:22 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 17:40 UTCVendor advisory
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 13:39 UTCVendor advisory
- 2026-09-18 09:37 UTCVendor advisory
- 2026-09-18 05:35 UTCVendor advisory
- 2026-09-18 01:34 UTCVendor advisory
- 2026-09-17 21:33 UTCEG score recompute
- 2026-09-17 21:33 UTCVendor advisory
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-17 17:31 UTCVendor advisory
- 2026-09-17 13:29 UTCVendor advisory
- 2026-09-17 09:28 UTCVendor advisory
- 2026-09-17 05:26 UTCVendor advisory
- 2026-09-17 01:24 UTCVendor advisory
- 2026-09-16 21:23 UTCVendor advisory
- 2026-09-16 17:21 UTCEG score recompute
- 2026-09-16 17:21 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 13:17 UTCVendor advisory
- 2026-09-16 09:13 UTCVendor advisory
- 2026-09-16 05:11 UTCEG score recompute
- 2026-09-16 05:11 UTCVendor advisory
- 2026-09-16 05:05 UTCEPSS rescore
- 2026-09-16 01:09 UTCVendor advisory
- 2026-09-15 21:08 UTCVendor advisory
- 2026-09-15 17:05 UTCVendor advisory
- 2026-09-15 13:03 UTCVendor advisory
- 2026-09-15 09:02 UTCVendor advisory
- 2026-09-15 05:00 UTCEG score recompute
- 2026-09-15 05:00 UTCVendor advisory
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-15 00:54 UTCVendor advisory
- 2026-09-14 20:52 UTCVendor advisory
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 16:50 UTCVendor advisory
- 2026-09-14 12:48 UTCVendor advisory
- 2026-09-14 08:47 UTCVendor advisory
- 2026-09-14 04:45 UTCVendor advisory
- 2026-09-14 00:44 UTCVendor advisory
- 2026-09-13 20:43 UTCEG score recompute
- 2026-09-13 20:43 UTCVendor advisory
- 2026-09-13 16:41 UTCEPSS rescore
- 2026-09-13 16:40 UTCVendor advisory
- 2026-09-13 12:39 UTCVendor advisory
- 2026-09-13 08:38 UTCVendor advisory
- 2026-09-13 04:36 UTCVendor advisory
- 2026-09-13 00:34 UTCVendor advisory
- 2026-09-12 20:32 UTCVendor advisory
- 2026-09-12 16:30 UTCVendor advisory
- 2026-09-12 12:28 UTCVendor advisory
- 2026-09-12 08:27 UTCVendor advisory
- 2026-09-12 04:26 UTCVendor advisory
- 2026-09-12 00:25 UTCVendor advisory
- 2026-09-11 20:24 UTCVendor advisory
- 2026-09-11 18:49 UTCCISA KEV update
- 2026-09-11 16:22 UTCEG score recompute
- 2026-09-11 16:22 UTCVendor advisory
- 2026-09-11 14:46 UTCEPSS rescore
- 2026-09-10 19:28 UTCCISA KEV update
- 2026-09-10 12:08 UTCEG score recompute
- 2026-09-10 09:26 UTCEPSS rescore
- 2026-09-09 20:01 UTCVendor advisory
- 2026-09-09 19:08 UTCCISA KEV update
- 2026-09-09 15:59 UTCVendor advisory
- 2026-09-09 11:57 UTCVendor advisory
- 2026-09-09 03:54 UTCVendor advisory
- 2026-09-08 23:52 UTCEG score recompute
- 2026-09-08 23:52 UTCVendor advisory
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 15:49 UTCVendor advisory
- 2026-09-08 11:43 UTCVendor advisory
- 2026-09-08 07:39 UTCVendor advisory
- 2026-09-08 03:36 UTCVendor advisory
- 2026-09-07 23:34 UTCVendor advisory
- 2026-09-07 19:32 UTCVendor advisory
- 2026-09-07 11:29 UTCVendor advisory
- 2026-09-07 07:27 UTCVendor advisory
- 2026-09-07 03:23 UTCVendor advisory
- 2026-09-06 23:22 UTCVendor advisory
- 2026-09-06 19:19 UTCVendor advisory
- 2026-09-06 15:17 UTCEG score recompute
- 2026-09-06 15:17 UTCVendor advisory
- 2026-09-06 11:15 UTCVendor advisory
- 2026-09-06 03:11 UTCVendor advisory
- 2026-09-05 23:09 UTCVendor advisory
- 2026-09-05 19:07 UTCEG score recompute
- 2026-09-05 19:07 UTCVendor advisory
- 2026-09-05 15:06 UTCVendor advisory
- 2026-09-05 11:04 UTCVendor advisory
- 2026-09-05 06:59 UTCVendor advisory
- 2026-09-05 02:57 UTCVendor advisory
- 2026-09-04 22:52 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.